Bug#3061: No more logs since cron.weekly rotation
Guy Maor said:
> Package: syslogd
> Version: 1.3-2
> The bug is in syslogd - the last line of the /etc/cron.weekly/sysklogd
> script reads "/etc/init.d/sysklogd reload". Presumably this
> UNDOCUMENTED reload command has the same effect as sending a SIGHUP to
> syslogd. Except it doesn't.
I disagree. I was having the same problem, and removed the leading '-' from
the log file names in /etc/syslog.conf, and the problem went away. I suspect
this new feature of syslogd (the '-' meaning not to immediately flush the
files after each entry) is broken.
--
Scott Barker
Linux Consultant
scott@galileo.cuug.ab.ca
http://www.cuug.ab.ca:8001/~barkers/ (under construction)
[ I try to reply to all e-mail within 5 days. If you don't ]
[ get a response by then, I probably didn't get your e-mail ]
[ (we have a sometimes sporadic connection to the internet) ]
"The doctrine of human equality reposes on this: that there is no man really
clever who has not found that he is stupid."
- G. K. Chesterton
Reply to: