Bug 440202

Summary: logrotate causes segmentation faults
Product: Red Hat Enterprise Linux 4 Reporter: Milos Malik <mmalik>
Component: logrotateAssignee: Tomas Smetana <tsmetana>
Status: CLOSED ERRATA QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 4.6   
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Fixed In Version: RHBA-2008-0703 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2008-07-24 19:52:20 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Description Milos Malik 2008-04-02 08:39:16 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; cs-CZ; rv: Gecko/20080325 Fedora/ Firefox/

Description of problem:
Logrotate doesn't recognize the name of the file and does something weird.

When the first line of the config file contains "some_log_file {" instead of "./some_log_file {" it causes segmentation fault too, but the message before crash is:

error: config:1 unknown option 'some' -- ignoring line
error: config:1 unexpected text
error: config:4 unexpected }
*** glibc detected *** double free or corruption (!prev): 0x4000000000010ae0 ***

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

How reproducible:

Steps to Reproduce:
1. create a temporary directory
2. enter this directory
3. create a file with name "config"
4. write following 4 lines into the file and save it
   ./some_log_file {
     maxage 3
5. touch ./some_log_file
6. logrotate -f -s status config

Actual Results:
# logrotate -f -s status config
error: config:1 lines must begin with a keyword or a filename (possibly in double quotes)
error: config:4 unexpected }
Segmentation fault

Expected Results:
Rotation of the file "some_log_file".

Additional info:
This problem was observed on following machines:


Comment 5 errata-xmlrpc 2008-07-24 19:52:20 UTC
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.