Bug 60341

Summary: Does not uncompress files before mailing as per man page
Product: [Retired] Red Hat Linux Reporter: Charles Seraphine <charles.seraphine>
Component: logrotateAssignee: Elliot Lee <sopwith>
Status: CLOSED NOTABUG QA Contact: Aaron Brown <abrown>
Severity: medium Docs Contact:
Priority: medium    
Version: 7.1   
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2002-02-26 01:01:13 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Charles Seraphine 2002-02-26 01:01:09 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.7) Gecko/20011226

Description of problem:
The man page implies that compressed logfiles will be mailed uncompressed.  This
is not the case; if you turn on compression, then logrotate will not decompress
the log before mailing.  This makes parsing the log file at your automated
log-collector darn tricky.

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


How reproducible:
Always

Steps to Reproduce:
1.Set mail and compress directives in logrotate config file
2.Run logrotate


	

Actual Results:  The file will be sent in compressed form (if sendmail doesn't gag).

Expected Results:  The file should be decompressed before being sent.

Additional info:

Excerpt from the man page:

They  are
       rotated whenever is grows over 100k is size, and the old logs files
       are mailed (uncompressed) to www after going through 5 rota-
       tions, rather then being removed.


Ideally, the feature should be implemented as described.  Failing that, we
should at least fix the man page to reflect reality.

Comment 1 Elliot Lee 2002-04-15 19:20:07 UTC
From reading the logwatch code, it appears that it only uncompresses mailed logs
if you use the 'mailfirst' keyword. I'm going to assume that there are good
reasons for this, and leave it as-is.