Bug 111553 - logrotate: mailfirst and delaycompress do not work together
Summary: logrotate: mailfirst and delaycompress do not work together
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: logrotate
Version: 8.0
Hardware: i386
OS: Linux
low
low
Target Milestone: ---
Assignee: Elliot Lee
QA Contact: David Lawrence
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2003-12-05 11:20 UTC by Ales Ledvinka
Modified: 2005-10-31 22:00 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2003-12-17 21:11:26 UTC
Embargoed:


Attachments (Terms of Use)

Description Ales Ledvinka 2003-12-05 11:20:24 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4)
Gecko/20030624

Description of problem:
using mailfirst and delaycompress nothing is mailed.
an attemtpt to mail nonexistent file is made. (with compressed extension)


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

How reproducible:
Always

Steps to Reproduce:
0.cat apachewebalizer
/usr/local/apache2/logs/access_log {
        compress
        create 644 root root
#       copytruncate
        daily
        delaycompress
        ifempty
        mail root@localhost
        mailfirst
        nomissingok
        noolddir

        prerotate
        endscript

        postrotate
        endscript

        rotate 9
        size 1500M
        sharedscripts
        start 0
}
1.logrotate -f -s /tmp/stav /etc/logrotate.d/apachewebalizer
2.
3.


Actual Results:  logrotate -f -s /tmp/stav
/etc/logrotate.d/apachewebalizer
sh: line 1: /usr/local/apache2/logs/access_log.0.gz: No such file or
directory
Failed to mail /usr/local/apache2/logs/access_log.0.gz to root@localhost!


Expected Results:  probably best: mail access_log.1.gz


Additional info:

Comment 1 Elliot Lee 2003-12-17 21:11:26 UTC
I'm pretty sure I've seen this bug before and that it has been fixed
since 8.0. Please upgrade...


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