/etc/logrotate.d/consolekit should not have compress option

Bug #840314 reported by Jérôme on 2011-09-03
This bug affects 1 person
Affects Status Importance Assigned to Milestone
consolekit (Ubuntu)

Bug Description

I think that log files compression lowers the system performance on desktop computers which have now enough disk space for storing old logs.

The "nocompress" and "compress" options of logrotate configure 2 different behaviours of logrotate.

If the log file isn't compressed,
logrotate will just rename it to something like 'log_file_name.log.1'
with quite no disk input/output.

If the log file is compressed,
logrotate will read the file, compress it and rewrite the content into a new file with a name like 'log_file_name.log.1.gz'.

I think that files compression is a good tradeoff only in case the compressed files have a longer lifetime than the log files (i. e. man pages, documentation, fonts, Debian package files, ...).

Drawbacks of log files compression :
- increases disk input/output
- increases cpu and memory usage
- increases energy consumption
- slightly decreases the disk lifetime

ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: consolekit 0.4.4-1
ProcVersionSignature: Ubuntu 2.6.38-11.48-generic
Uname: Linux 2.6.38-11-generic x86_64
Architecture: amd64
Date: Sat Sep 3 14:54:13 2011
InstallationMedia: Lubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427)
SourcePackage: consolekit
UpgradeStatus: No upgrade log present (probably fresh install)

Jérôme (jerome-bouat) wrote :
Jérôme (jerome-bouat) wrote :

This becomes more important with SSD disks whose lifetime depends on the number of write cycles.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers