Re: [gentoo-user] syslog-ng-3.4: time_sleep() deprecated or not?
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 (€) -- Dan Johansson, http://www.dmj.nu *** This message is printed on 100% recycled electrons! *** 0x2FB894AD.asc Description: application/pgp-keys signature.asc Description: OpenPGP digital signature
Re: [gentoo-user] syslog-ng-3.4: time_sleep() deprecated or not?
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 -- Regards, Mick signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] syslog-ng-3.4: time_sleep() deprecated or not?
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 signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] syslog-ng-3.4: time_sleep() deprecated or not?
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...
Re: [gentoo-user] syslog-ng-3.4: time_sleep() deprecated or not?
On Wed, Jul 10, 2013 at 03:32:16PM +0100, Mick wrote: 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? Did you try less /var/log/syslog.log ? -- Happy Penguin Computers ') 126 Fenco Drive ( \ Tupelo, MS 38801 ^^ supp...@happypenguincomputers.com 662-269-2706 662-205-6424 http://happypenguincomputers.com/ A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail? Don't top-post: http://en.wikipedia.org/wiki/Top_post#Top-posting
[gentoo-user] syslog-ng-3.4: time_sleep() deprecated or not?
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? Jarry -- ___ This mailbox accepts e-mails only from selected mailing-lists! Everything else is considered to be spam and therefore deleted.
