** Description changed: - Since upgrade to jaunty I have problems with one desktop (9.04/amd-64). + IMPACT: + If logrotate is unable to find the logs it is expecting, it will incorrectly rotate /dev/null -> /dev/null. This can cause the session to become totally locked. Login is not possible (see bug #270781). - The session was running for several hours/days and the screen-locker has locked the terminal. - Login is not possible (see https://bugs.launchpad.net/ubuntu/+source/pam/+bug/270781). - The cause is that /dev/null is replaced with a "normal" file. - The original /dev/null is moved to /dev/null.1 + ADDRESSED: + A patch cherry picked from >Maverick packages resolves the config parsing when the wildcard produces an empty set (which defaulted to /dev/null). - This issue is intended to track down the cause which leads to the - corruption of the /dev/null device. + PATCH: + See Merge proposal + + TEST CASE: + Install apache2-commons (which includes a logrotate config), but have no apache running -> therefore no logs to rotate. Wait, or induce a log rotation and witness /dev/null be rotated to /dev/null.1. + + REGRESSION POTENTIAL: + This should be considered low, the attached resolution has been in Debian since March 2010 and is in the Maverick release.
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/387189 Title: logrotate incorrectly rotates /dev/null to /dev/null.1 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
