| 1 |
On Wednesday 10 Jul 2013 11:30:08 Mick wrote: |
| 2 |
> On Wednesday 10 Jul 2013 11:15:13 Dan Johansson wrote: |
| 3 |
> > On 09.07.2013 20:00, Jarry wrote: |
| 4 |
> > > Hi Gentoo-users, |
| 5 |
> > > |
| 6 |
> > > today I updated syslog-ng on my server. When I checked config |
| 7 |
> > > file, I got this message: |
| 8 |
> > > |
| 9 |
> > > # /etc/init.d/syslog-ng checkconfig |
| 10 |
> > > * Checking your configfile (/etc/syslog-ng/syslog-ng.conf) ... |
| 11 |
> > > WARNING: Your configuration file uses an obsoleted keyword, please |
| 12 |
> > > update your configuration; keyword='time_sleep', change='time_sleep() |
| 13 |
> > > has been deprecated since syslog-ng 3.3' [ ok ] |
| 14 |
> > > # |
| 15 |
> > > |
| 16 |
> > > So I checked the new syslog-ng-ose-v3.4-guide-admin.pdf, |
| 17 |
> > > but there is nothing about time_sleep() being obsolete |
| 18 |
> > > or deprecated. Quite on the contrary: it is listed as |
| 19 |
> > > valid option, and even mentioned in the chapter 17 |
| 20 |
> > > "best practices" as a way of handling lots of parallel |
| 21 |
> > > connections. |
| 22 |
> > > |
| 23 |
> > > So how is it then? Is time_sleep() supported and valid, |
| 24 |
> > > or obsolete/deprecated? |
| 25 |
> > |
| 26 |
> > I also had some issues when I upgraded to 3.4. |
| 27 |
> > Most of the warnings went away when I changed the version string in |
| 28 |
> > syslog-ng.conf to "@version: 3.4". |
| 29 |
> > |
| 30 |
> > Just my 2 cents (€) |
| 31 |
> |
| 32 |
> The new version runs a couple of useful checks on the syntax of the |
| 33 |
> configuration file - who would have thought that I had a duplicate |
| 34 |
> directive in there! O_o |
| 35 |
|
| 36 |
Hmm ... I just tried 'less /var/log/syslog' and I now get a binary file ... |
| 37 |
|
| 38 |
However, most parses it as text. Has something changed in less recently? |
| 39 |
-- |
| 40 |
Regards, |
| 41 |
Mick |
Archives