Bug 982635 - Missing required "compress" option in httpd logrotate configuration file
Missing required "compress" option in httpd logrotate configuration file
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: httpd (Show other bugs)
All Linux
unspecified Severity medium
: rc
: ---
Assigned To: Web Stack Team
BaseOS QE Security Team
Depends On:
  Show dependency treegraph
Reported: 2013-07-09 09:10 EDT by Florian Crouzat
Modified: 2013-07-09 09:29 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2013-07-09 09:29:43 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Florian Crouzat 2013-07-09 09:10:25 EDT
Description of problem:

/etc/logrotate.d/httpd contains "delaycompress" to postpone compression of the rotated logs but it is missing the "compress" option which is required when using "delaycompress" as "man logrotate.conf" states:

              Postpone compression of the previous log file to the next rotation cycle. This only has effect when used in combination with compress.  It  can be used when some program cannot be told to close its logfile and thus might continue writing to the previous log file for some time.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. yum install httpd
2. service httpd start
3. # generate logs
4. logrotate --force /etc/logrotate.d/httpd

Actual results:

Rotated files are not compressed

Expected results:

Rotated files are compressed with a delay.

Additional info:

# grep compress /etc/logrotate.d/httpd
Comment 1 Joe Orton 2013-07-09 09:29:43 EDT
This is not a bug.  If compress is enabled globally (administrator preference), delaycompress must also be used for httpd log files.  If compress is not enabled globally, it has no effect.

Note You need to log in before you can comment on or make changes to this bug.