Description of problem: When logrotate finishes, cupsd appends logs to <logfile>.1 and doesn't use newly created logfile until the service is restarted. https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=215023 reveals why this is the case, so i guess my problem is already known. The RPM-changelog mentions bug 215024, but i'am not allowed to access this information :-/ What is it that cupsd cant't get reloaded by logrotate? Version-Release number of selected component (if applicable): cups-1.2.7-1.7.fc6 How reproducible: Not hard. Steps to Reproduce: 1. rotate logs 2. ll -t /var/log/cups/ BTW, MaxLogSize=2000000000 is afaics not the upstream default and I would like to know why 2G should be a good idea.
Okay, the solution to this is to get CUPS to rotate its own logs and leave logrotate out of it altogether. It's no good trying to get logrotate to reload CUPS because it'll restart any long-running print jobs, possibly wasting hundreds of sheets of paper.
(In reply to comment #1) > Okay, the solution to this is to get CUPS to rotate its own logs and leave > logrotate out of it altogether. Sounds good. Thanks for your immediate reply..do you have a comment on the MaxLogSize entry in cupsd.conf, please?
We'll drop the size down so that cups ends up rotating its own logs. It was set at 2Gb just to avoid LFS problems IIRC.
Fixed in devel: 1.2.7-8.fc7.