Issue Type: Bug Bug
Affects Versions: 1.0.11
Assignee: Logback dev list
Created: 04/Nov/13 11:12 AM
Description:

I have an embedded device logging performance data in a 30 second interval with a hourly rollover and enabled compression (zip). In case the application is stopped at rollover and started later on the old file does not get compressed.

This is slightly related to LOGBACK-162 which was about not deleting old files when the application was stopped at rollover.

I would highly appreciate if it were made impossible to have any uncompressed files except the current one.

As a solution I'd propose that when cleanHistoryOnStart is set to true, a scan through the history is performed (probably already implemented) and in case an uncompressed file is found the compression is triggered.

Thanks a lot,
Alex

Environment:

Debian Linux 2.6.26, Tomcat 6.0.28, SLF4J 1.7.5, Logback 1.0.11

Project: logback
Priority: Major Major
Reporter: Alexander Lauper
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
logback-dev mailing list
logback-dev@qos.ch
http://mailman.qos.ch/mailman/listinfo/logback-dev

Reply via email to