I confirm the problem with /usr/sbin/syslogd-listfiles script, which
should check that the log file does not exist.
I do not like much the solution of Guillaume Pancak to recreate missed
files, as I want to keep the log directory as clean as possible. Script
should be more robust. Reto, thanks
In my case, the problem was caused by additional spaces behind the
filesnames in /etc/syslog.conf
The files generated in /var/log were the filenames without spaces, but
syslogd-listfiles tries a 'stat' on the filename *with* space.
Perhaps this could be improved by stripping trailing spaces f
Same problem here.
Version 1.5-5 on lenny, i386.
I've got 3 systems running lenny, but only my server shows this
behaviour. Every day i get this error from cron.
Greetings,
timbo
kiste:~# apt-cache show sysklogd
Package: sysklogd
Priority: extra
Section: admin
Installed-Size: 212
Maintainer:
Package: sysklogd
Version: 1.5-5
Severity: normal
When /usr/sbin/syslogd-listfiles is run the following message is generated on
several computers:
Use of uninitialized value in numeric ge (>=) at /usr/sbin/syslogd-listfiles
line 129.
All systems on which this script is run use lenny, and diff
4 matches
Mail list logo
