logrotate incorrectly rotates /dev/null to /dev/null.1
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
apache2 (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Hardy |
Invalid
|
Undecided
|
Unassigned | ||
Karmic |
Invalid
|
Undecided
|
Unassigned | ||
Lucid |
Invalid
|
Undecided
|
Unassigned | ||
logrotate (Ubuntu) |
Fix Released
|
High
|
Canonical Server | ||
Hardy |
Won't Fix
|
High
|
Unassigned | ||
Karmic |
Won't Fix
|
High
|
Unassigned | ||
Lucid |
Fix Released
|
High
|
Unassigned |
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.
Related branches
- Chuck Short (community): Approve
- Ubuntu Stable Release Updates Team: Pending requested
-
Diff: 74 lines (+54/-0)3 files modifieddebian/changelog (+8/-0)
debian/patches/parser571033.patch (+45/-0)
debian/patches/series (+1/-0)
tags: | added: jaunty |
Changed in ubuntu: | |
status: | New → Confirmed |
Changed in ubuntu: | |
status: | New → Incomplete |
status: | Incomplete → New |
affects: | ubuntu → logrotate (Ubuntu) |
tags: | added: patch |
Changed in logrotate (Ubuntu): | |
assignee: | nobody → Canonical Server Team (canonical-server) |
summary: |
- /dev/null corrupted (/dev/null.1) + logrotate incorrectly rotates /dev/null to /dev/null.1 |
description: | updated |
Changed in logrotate (Ubuntu Hardy): | |
importance: | Undecided → High |
status: | New → Confirmed |
Changed in logrotate (Ubuntu Karmic): | |
importance: | Undecided → High |
status: | New → Confirmed |
Changed in logrotate (Ubuntu Lucid): | |
importance: | Undecided → High |
status: | New → Confirmed |
Changed in logrotate (Ubuntu Karmic): | |
status: | Confirmed → Won't Fix |
Second desktop shows the problem (also 9.04/amd-64) after being hibernated 4 or 5 times.