-----BEGIN PGP SIGNED MESSAGE----- The solution is quite simple actually: here's what i've found in /etc/logfiles (SuSE 6.4) # # This file tells cron.daily, which log files have to be watched # # File max size mode ownership service # (reload if changed) and then it goes something like: /var/log/httpd/access_log +4096k 644 root.root apache So you could add to /var/log/messages, or whatever you use, syslogd - --- Bogdan Zapca System Administrator SC EcoSoft SA Internet Service Provider 1-7 Deva st, Cluj-Napoca, Romania Tel: +40 64 199696 PGP: http://www.itotal.ro/lupe@admin2.ecosoft.ro.pgp http://www.ecosoft.ro On Thu, 3 Aug 2000, Br�ulio Gergull wrote:
I'm having the following problem:
Whenever cron gzip's my messages file, all logging to the "new" messages file is stopped, no information is entered.
I have a similar situation here, however just the mail log stops after logrotate runs.
The only solution I found sofar is rebooting the machine, there has to be a simpler solution !
You don't need to reboot, just restart syslogd:
/sbin/init.d/syslog restart
However this is not a solution. I've posted this question before but gotno answers.
I'm running SuSE 6.3.
rgrds, Br�ulio Gergull
--------------------------------------------------------------------- To unsubscribe, e-mail: suse-security-unsubscribe@suse.com For additional commands, e-mail: suse-security-help@suse.com
-----BEGIN PGP SIGNATURE----- Version: 2.6.3i Charset: noconv iQCVAwUBOYplo9Pv6ylvTc6pAQFDuQP/cjtSwSqZOJILupWbGK5A+bsalBWV+grP 0Bwdgf+VkB6xroQjM1sx5bF0d8RBVfoyFXGCCbHULxOZsDPF+EDuhq25S5pWNwvg I86yZ8zYBSLLhca32HzktWVsj6Ve4Q4YU79lNU/kiTzSjSav3We6jpo/zzrGFVHN q0eNqXrRDms= =bV0c -----END PGP SIGNATURE-----