I'm wondering about something that has been bugging me for a while with one of my systems, it seems that when the log file(s) get full and it moves them into .gz format it doesn't want to continue writing to the logs. It's currently running SuSE 6.3 which I plan on updating eventually to 7.3 as soon as I rope in all the configurations and changes I made so that I can duplicate them consistantly again. But for the time being, I would like to figure out why the log files arn't continuing to be written to. -- S.Toms - smotrs@mindspring.com - www.mindspring.com/~smotrs SuSE Linux v7.2 - Kernel 2.4.4-4GB I went to the race track once and bet on a horse that was so good that it took seven others to beat him!
I vaguely remember something like this happening to me at some point. If I remember, I had to restart syslogd (/etc/init.d/syslog restart) for it start logging again, but I can't be sure. The path above is on 7.3, it's probably something different on 6.3 (maybe /etc/rc.d/syslog). Regards, Keith On Fri, Feb 08, 2002 at 06:05:07PM -0800, S.Toms wrote:
I'm wondering about something that has been bugging me for a while with one of my systems, it seems that when the log file(s) get full and it moves them into .gz format it doesn't want to continue writing to the logs. It's currently running SuSE 6.3 which I plan on updating eventually to 7.3 as soon as I rope in all the configurations and changes I made so that I can duplicate them consistantly again. But for the time being, I would like to figure out why the log files arn't continuing to be written to.
On Fri, Feb 08, 2002 at 06:05:07PM -0800, S.Toms wrote:
But for the time being, I would like to figure out why the log files arn't continuing to be written to.
The logging daemon, syslogd, keeps an open filehandle to the files. It keeps writing to the files, even after a move or a rename. You can even delete the file and the process keeps writing to the file. This file even takes up space on the hard disk without showing in a 'ls'. NB: This is true for most process on a Un*x system, not only syslogd. The trick is to move the logfiles, tell the process to reopen it's files and only then do something with the files. With syslogd: send a kill -HUP [pid syslogd] Regards, Cees.
participants (3)
-
Cees van de Griend
-
Keith Winston
-
S.Toms