On Fri, 17 Mar 2000, Morten Christensen wrote:
I have a file- and printserver running Suse 6.3.
It has suddenly stopped writing to the logfiles.
The files /var/log/mail and /var/log/messages are empty and have the date when the logging stopped.
With same date as the empty log-files is gz-files with the peviusly periods logfiles archived.
The /var-partition has 400 M unused diskplace.
Okay, my first thought was space, but you already have that covered. The dumping of old data to a gz file is done by a cron script about midnight. The same script also deletes sufficiently-old gz files, I believe. But it sounds like it is NOT telling the syslog daemon to reinitialize. Try this command: killall -HUP syslogd Then look at /var/log/messages and see if it has a new line at the bottom (syslogd logs the fact that it was reinitialized). If that takes care of the problem, then investigate your cron configuration, along with /etc/logfiles, to see why that action doesn't happen automatically. -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/