[TriLUG] logrotate misery

John Reuning john at ibiblio.org
Fri Feb 27 12:19:30 EST 2004


This is good advice.  logrotate actually copies the contents of each .#
log file to the next highest number as it rotates the logs.  For heavily
loaded production systems or systems with slow disk i/o, this can make
it grind to a halt.  logrotate has caused a couple of my less hardy
systems to crash.

If you need to keep historic log files, a rotation system that date
stamps and compresses works well.

Thanks,

-jrr

> Check each of the directories that are being rotated and each of the
> files.  Look for a directory with lots of files or a very, very large
> file.





More information about the TriLUG mailing list