Created attachment 602812 [details] Possible patch for logrotate's filenames support +++ This bug was initially created as a clone of Bug #770131 +++ Description of problem: For processing archived squid logs, loghtparser.pl supports "lightparse.pl access.log.{\d}.{gz|bz2}" syntax. But logrotate creates files named "access.log-NNNNNNNN.gz", not "access.log.NNNNNNNN.gz", so it's impossible to process those files; lightparser.pl silently ignores filename and processes access.log. Version-Release number of selected component (if applicable): lightsquid-apache-1.8-11.fc17.noarch Solution: Possible patch to allow logrotate's file format is attached
This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '17'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 17's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 17 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 17's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.