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 the call cron -r cron /etc/crontab cron -l shows the changes Michael -----Original Message----- From: r.hegewald [mailto:rh@medoil.de] Sent: Monday, September 17, 2001 9:37 AM To: Graham Jones; spiekey Cc: suse-security@suse.com Subject: Re: [suse-security] SuSE is not logging anymore.. At 14:16 14.09.2001 +0200, Graham Jones wrote:
Hello,
On Fri, 14 Sep 2001, spiekey wrote:
Hello! what could be the reason that suse won´t write into my /var/log/messages anymore? The last activity was from the 11th of September. Anyone any idea?
I have got the same problem: Whenever some program (or script?) compresses /var/log/messages a new messages file is created but always with 0 values. Nothing is written to it. I have to restart syslog and then it works fine. That also happens with /var/log/mail. I use SuSe version 6.3 Richard Hegewald -- To unsubscribe, e-mail: suse-security-unsubscribe@suse.com For additional commands, e-mail: suse-security-help@suse.com