Logrotate does what it says. Rotate log files. This is most certainly needed or you logfiles will fill your drive. Why it's not finishing? I've never seen that, maybe it's looking for a log file that's not there or there is some other process that is hanging it. After it rotates the file it sends the -HUP to the program that logs to the file. If that program hangs maybe that would cause logrotate to hang.
-----Original Message----- From: Keith Soares [mailto:[EMAIL PROTECTED] Sent: Thursday, August 07, 2003 10:15 AM To: [EMAIL PROTECTED] Subject: Logrotate: 2 questions 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. 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? Thanks! --- Keith Soares Bean Creative -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED] https://www.redhat.com/mailman/listinfo/redhat-list
