Public bug reported:

Binary package hint: logrotate

I'm seeing logrotate use 100% CPU for a couple of minutes daily!

I've tracked this issue to "logrotate.status" being ~57MB, having one
million lines, almost all of them mentioning log files that are now non-
existent (I had an accident where millions of files were created once).
I believe the correct behavior is for logrotate to "clean" its status
file removing lines that reference non existent files. If logrotate
itself doesn't do that, can we have a cronjob to do it be default.

** Affects: logrotate (Ubuntu)
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/730504

Title:
  100% CPU due to non-existent entries in logrotate.status

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to