Hi..
At 11:33 31-10-2001 +0100, Markus Gaugusch wrote:
My Syslog stopped logging since the 19th of October. I can almost
swear that it was logging after the 19th of October, cause i would
have realised it! It´s not very big at all, i have a few GB left on my
HD, so that shouldn´t be a problem, too.
if you start syslogd, is there a message in the /var/log/messages about
it?
Is /dev/log ok?
do "rpm -Vv `rpm -qf `which syslogd``"
Markus Gaugusch
I thing it is because of cron script compressing log files after getting to
big. Look at "Appeldorn" " anser:
/*----------------*/
syslogd and e.g. sendmail will loose theire
file handle cauz file moved to *.gz e.g.
so they have to be restarted with SIGHUP
killall -HUP sendmail
killall -HUP syslogd
a cron job (/etc/crontab) is crunching the
log file regulary. Simply add in crontab e.g.
#
-*/15 * * * * root test -x /usr/lib/cron/run-crons &&
/usr/lib/cron/run-cron && killall -HUP syslogd && killall -HUP sendmail
to restart the daemons
/*----------------------*/
That is because after crunching file a new message (and mail) file is
created, and its handle is quite different from the old one (and the old
handle is in use by syslogd) - so syslogd have to be at least reloaded...
Regards
Marcin Gryszczuk
