From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 46F3A1381F3 for ; Wed, 10 Jul 2013 15:01:08 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 4575EE09FF; Wed, 10 Jul 2013 15:01:02 +0000 (UTC) Received: from farlander.net (farlander.net [178.79.169.98]) (using TLSv1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 2905EE096D for ; Wed, 10 Jul 2013 15:01:01 +0000 (UTC) Received: from station-gentoo-89r (ppp83-237-105-17.pppoe.mtu-net.ru [83.237.105.17]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by farlander.net (Postfix) with ESMTPSA id 1452312BF2 for ; Wed, 10 Jul 2013 15:00:58 +0000 (UTC) Date: Wed, 10 Jul 2013 19:00:50 +0400 From: Andrew Tselischev To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] syslog-ng-3.4: time_sleep() deprecated or not? Message-ID: <20130710150050.GA8051@station-gentoo-89r> Mail-Followup-To: gentoo-user@lists.gentoo.org References: <51DC4FC5.5070409@gmail.com> <51DD3431.4090006@dmj.nu> <201307101130.18950.michaelkintzios@gmail.com> <201307101532.41316.michaelkintzios@gmail.com> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <201307101532.41316.michaelkintzios@gmail.com> User-Agent: Mutt/1.5.21 (2010-09-15) X-Archives-Salt: 3c5b2d83-f056-44f2-b0a3-f156a2eda248 X-Archives-Hash: f61b9e7b5fac9f20ca76163f315079c0 On Wed, Jul 10, 2013 at 03:32:16PM +0100, Mick wrote: > On Wednesday 10 Jul 2013 11:30:08 Mick wrote: > > On Wednesday 10 Jul 2013 11:15:13 Dan Johansson wrote: > > > On 09.07.2013 20:00, Jarry wrote: > > > > Hi Gentoo-users, > > > > > > > > today I updated syslog-ng on my server. When I checked config > > > > file, I got this message: > > > > > > > > # /etc/init.d/syslog-ng checkconfig > > > > * Checking your configfile (/etc/syslog-ng/syslog-ng.conf) ... > > > > WARNING: Your configuration file uses an obsoleted keyword, please > > > > update your configuration; keyword='time_sleep', change='time_sleep() > > > > has been deprecated since syslog-ng 3.3' [ ok ] > > > > # > > > > > > > > So I checked the new syslog-ng-ose-v3.4-guide-admin.pdf, > > > > but there is nothing about time_sleep() being obsolete > > > > or deprecated. Quite on the contrary: it is listed as > > > > valid option, and even mentioned in the chapter 17 > > > > "best practices" as a way of handling lots of parallel > > > > connections. > > > > > > > > So how is it then? Is time_sleep() supported and valid, > > > > or obsolete/deprecated? > > > > > > I also had some issues when I upgraded to 3.4. > > > Most of the warnings went away when I changed the version string in > > > syslog-ng.conf to "@version: 3.4". > > > > > > Just my 2 cents (€) > > > > The new version runs a couple of useful checks on the syntax of the > > configuration file - who would have thought that I had a duplicate > > directive in there! O_o > > Hmm ... I just tried 'less /var/log/syslog' and I now get a binary file ... > > However, most parses it as text. Has something changed in less recently? > -- > Regards, > Mick No, I think it's syslog-ng that puts null bytes in the log at startup. Now I wonder, was it intended to be a feature or what...