I think that I just found a "real" solution. In the logrotate.conf file, under the section that you are concerned about (in my case, the one for my firewall log) use the "postrotate/endscript" pair. For example: [...] postrotate /sbin/killall -HUP syslogd /sbin/killall -HUP klogd endscript [...] Does that make sense? At 07:05 PM 10/9/00, Scott, David wrote:
I've been having the same problem (in both 6.1 and 6.4). As a workaround I set cron to do a killall -HUP syslogd after rotating the logs.
I'd be really interested in a real solution tho.
David Scott
-----Original Message----- From: Geordon VanTassle [mailto:admin@thecoventree.com] Sent: Monday, October 09, 2000 3:35 PM To: SuSE Linux Mailing List Subject: [SLE] Logrotate not re-init logging daemon?
Ok, folks, here's one for you: I have logrotate set up to rotate my firewall log every night and mail me a copy. However, it seems that either klogd or syslogd does not continue logging to the file "/var/log/firewall" after being rotated.
Any ideas?
TIA, Geordon All prayers are answered. However, sometimes the answer is "No."
-- 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/faq
-- 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/faq
-- 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/faq