The problem is caused by logrotate. As soon as logrotate takes the error_log away from CUPS, CUPS needs to open a new error_log and does not succeed.
Either we must hack CUPS, so that it sets our ownerships (so that it re- opens the file as normal user without problem) or we must make logrotate placing an empty error_log with correct ownerships, after it has taken away the old file. Probably the CUPS solution is the better one, as otherwise both CUPS and logrotate packages have to carry the information what the ownerships and permissions of error_log have to be. -- cupsd can't access /var/log/cups/error_log permission denied https://launchpad.net/bugs/54277 -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
