** Branch linked: lp:~davewalker/ubuntu/lucid/logrotate/lp387189
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to apache2 in ubuntu.
https://bugs.launchpad.net/bugs/387189
Title:
logrotate incorrectly rotates /dev/null to /dev/null.1
** Changed in: logrotate (Ubuntu)
Assignee: (unassigned) = Canonical Server Team (canonical-server)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to apache2 in ubuntu.
https://bugs.launchpad.net/bugs/387189
Title:
/dev/null
** Tags added: patch
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to apache2 in ubuntu.
https://bugs.launchpad.net/bugs/387189
Title:
/dev/null corrupted (/dev/null.1)
--
Ubuntu-server-bugs mailing list
This is a logrotate issue and happens if the specified logfile directory
(in this case /var/log/apache2) does not exist and the postrotate script
contains a closing '}'. Therefore I don't think Jonathan's patch would
fix the issue completely.
The full info is at http://bugs.debian.org/cgi-
OK. Do we have a test case for which my patch fails?
If the remaining issue is that my patch contains a closing '}', that is
easily solved, because the {} around the variable name are only there
for style reasons, and are not required.
Here is a modified patch without the {} . Is there a test
Based on comments #24 and #25 it looks like this is an Apache issue, so
I've added apache2 - apache2 maintainers please have a look because it's
got quite an impact.
Dave
** Also affects: apache2 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because
It seems to me a patch to /etc/logrotate.d/apache2 is the simplest
solution.
The attached diff tries to solve the issue and also be more readable,
breaking the one complex line involving backticks into three shorter
simpler lines, no backticks needed.
There are a lot of cases to test this with,
