Re: [gentoo-user] syslog-ng-3.4: time_sleep() deprecated or not?

[Andrew Tselischev]

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...