On Thu, 2003-08-07 at 10:15, Keith Soares wrote: > We have a RH Linux 7.3 web server that has what I believe to be a > default setup of logrotate running each night. > > My first question is: what is the purpose of the default > installation/setup of logrotate? What is it rotating? I ask because I > am getting frustrated with logrotate and ideally would like to kill > it, but don’t know yet what harm this may cause.
Uh, it rotates your logs. :) > What happens is that each night a 4:02am it runs, but it seems to take > a very long time to run and use a lot of resources. It shows up as > using over 94% of the CPU time in Running Processes (Webmin). Plus to > make matters worse, it doesn’t complete before the next instance runs, > so they continually build up (I’ve seen 7 or 8 instances at once > running) and this ends up severely slowing the system… > > So my second question is: has anyone seen this and can you give me > some pointers on correcting it? I've seen this with overloaded Perl scripts and the like, but I've never had that problem with logrotate. If you don't want your logs to rotate, simply delete the /etc/cron.daily/logrotate script (you might want to back it up). If I were you, though, I'd investigate what it seems to be choking on. The main logrotate configuration file is /etc/logrotate.conf. However, similar to xinetd, the per-service configuration files have been distributed into /etc/logrotate.d/ and sourced by the include statement in /etc/logrotate.conf. You might want to disable all of them manually, re-enabling one per night, until you find out what's causing your dilemma. Otherwise, you're eventually going to fill up /var with non-rotated system logs. HTH. -- Jason Dixon, RHCE DixonGroup Consulting http://www.dixongroup.net -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED] https://www.redhat.com/mailman/listinfo/redhat-list
