Hardy has seen the end of its life and is no longer receiving any
updates. Marking the Hardy task for this ticket as "Won't Fix".
** Changed in: logrotate (Ubuntu Hardy)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to logrotate in Ubuntu.
https://bugs.launchpad.net/bugs/387189
Title:
logrotate incorrectly rotates /dev/null to /dev/null.1
Status in “apache2” package in Ubuntu:
Invalid
Status in “logrotate” package in Ubuntu:
Fix Released
Status in “apache2” source package in Lucid:
Invalid
Status in “logrotate” source package in Lucid:
Fix Released
Status in “apache2” source package in Hardy:
Invalid
Status in “logrotate” source package in Hardy:
Won't Fix
Status in “apache2” source package in Karmic:
Invalid
Status in “logrotate” source package in Karmic:
Won't Fix
Bug description:
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).
ADDRESSED:
A patch cherry picked from >Maverick packages resolves the config parsing
when the wildcard produces an empty set (which defaulted to /dev/null).
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.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/387189/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
