Bug #3922
closed
- Status changed from 8 to Discussion
- Assignee changed from Nicolas PERRON to François ARMAND
Hmmm...it remind me that delaycompress was a problem before. See #2962, François Bayard had a problem with huge log files.
Do you plan to change something in jetty in order to stop writing in the file ?
- Status changed from Discussion to 8
- Assignee changed from François ARMAND to Matthieu CERDA
Nicolas PERRON wrote:
Hmmm...it remind me that delaycompress was a problem before. See #2962, François Bayard had a problem with huge log files.
Do you plan to change something in jetty in order to stop writing in the file ?
The point of this ticket is that it is necessary to use delaycompress for any logrotate configs that have a sharedscripts section. Bug #2962 was about the uncompressed logs taking up extra space - but it is clearly preferable to not drop logs than to save space: correctness comes before optimisation.
Please fix this ASAP.
- Status changed from 8 to In progress
Acknowledged. Task started.
- Status changed from In progress to Pending technical review
- Assignee changed from Matthieu CERDA to Jonathan CLARKE
- % Done changed from 0 to 100
- Pull Request set to https://github.com/Normation/rudder-techniques/pull/194
- Target version changed from 2.4.9 to 2.4.10
- Target version changed from 2.4.10 to 2.4.11
- Status changed from Pending technical review to Released
- Target version changed from 2.4.11 to 2.4.9
This bug has been fixed in Rudder 2.4.9 (but the issue has not been automatically updated), which was released today.
Check out:
- Subject changed from We don't use delaycompress in logrotate when we should to Logrotate should use 'delaycompress' option
- Project changed from 34 to Rudder
- Category set to Packaging
Also available in: Atom
PDF
Updated by Nicolas PERRON 
Updated by Jonathan CLARKE 
Updated by Matthieu CERDA 
Updated by