Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#29215 - [privoxy] Logrotate configuration contains too general logfile pattern, rotates rotated logfiles

Attached to Project: Community Packages
Opened by Tilman Blumenbach (Tblue) - Sunday, 01 April 2012, 07:50 GMT
Last edited by Lukas Fleischer (lfleischer) - Friday, 20 April 2012, 19:50 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Lukas Fleischer (lfleischer)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

Privoxy's logrotate configuration (/etc/logrotate.d/privoxy) uses a too general logfile pattern ("/var/log/privoxy/*"). The logrotate manpage says:

> Please use wildcards with caution. If you specify *, logrotate will rotate all files, including
> previously rotated ones.

That's exactly what's happening on my system: Logrotate rotates the already rotated logfiles, creating dozens of useless files. The pattern "/var/log/privoxy/logfile" should lead to a more sane behaviour (there's no jarfile anymore, as far as I can see).

Additional info:
* privoxy 3.0.19-2

Steps to reproduce:

Install privoxy, logrotate and a cron daemon amd observe that logrotate rotates already rotated privoxy logfiles.
This task depends upon

Closed by  Lukas Fleischer (lfleischer)
Friday, 20 April 2012, 19:50 GMT
Reason for closing:  Fixed
Additional comments about closing:  Fixed in 3.0.19-3.
Comment by Tilman Blumenbach (Tblue) - Sunday, 01 April 2012, 10:28 GMT
Oh, and if you still want to rotate the jarfile ("just in case"), there's the option "missingok" that ignores missing logfiles. See the logrotate manpage.

Loading...