Your answer is dead-on correct - thank you so much! --- Keith Soares Bean Creative
-----Original Message----- From: Gordon Messmer [mailto:[EMAIL PROTECTED] Sent: Thursday, August 07, 2003 10:59 AM To: [EMAIL PROTECTED] Subject: Re: Logrotate: 2 questions Keith Soares wrote: > 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... Apply all of the avilable errata. You probably have a release of mailman or samba that includes a bad logrotate script. To confirm the problem, cut and paste this command: grep '*' /etc/logrotate.conf /etc/logrotate.d/* If any of your logrotate files contain a pattern where '*' is at the end of a glob, then that belongs to a broken package. On my system, I get these results: /etc/logrotate.d/cups:/var/log/cups/*_log { /etc/logrotate.d/httpd:/var/log/httpd/*log { /etc/logrotate.d/samba:/var/log/samba/*.log { On each, the '*' is at the beginning of the filename, not the end. If the '*' appears at the end, logrotate will attempt to also rotate the files it has already rotated, and your log directory will eventually fill with thousands of log files. Figure out what directory now has all of those files, and clean it out like so: cd /var/log/mailman; find . -type f -name '*.1*' | xargs rm -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED] https://www.redhat.com/mailman/listinfo/redhat-list -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED] https://www.redhat.com/mailman/listinfo/redhat-list
