Bug 110291

Summary: logwatch hostname pattern match in cron analysis
Product: [Retired] Red Hat Linux Reporter: Need Real Name <jgd>
Component: logwatchAssignee: Elliot Lee <sopwith>
Status: CLOSED DUPLICATE QA Contact: David Lawrence <dkl>
Severity: medium Docs Contact:
Priority: medium    
Version: 9   
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-02-21 19:00:02 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:
Attachments:
Description Flags
Correction to pattern match for hostname field none

Description Need Real Name 2003-11-17 23:05:47 UTC
From Bugzilla Helper: 
User-Agent: Mozilla/5.0 (compatible; Konqueror/3.1; Linux) 
 
Description of problem: 
The hostname pattern match in /etc/log.d/scripts/services/cron is incorrect.  Any host 
which contains the character '-' in its name will get unmatched entries for things 
which would be otherwise ignored. 
 
Version-Release number of selected component (if applicable): 
logwatch-4.3.1-2 
 
How reproducible: 
Always 
 
Steps to Reproduce: 
1. Install redhat 9 on a host with a minus in its name (e.g. host-1.example.com) 
2. Wait until there are entries for cron.hourly in /var/log/cron 
3. Run /etc/cron.daily/00-logwatch 
     
 
Actual Results:  You will see unmatched entries for 'cron.hourly' runs in the email 
output by logwatch.  These entries are correctly skipped if the hostname does not 
contain a minus. 
 
Expected Results:  Invocations of cron.hourly should not show up in the email output 
by logwatch.

Comment 1 Need Real Name 2003-11-17 23:07:40 UTC
Created attachment 96035 [details]
Correction to pattern match for hostname field

Comment 2 Miloslav Trmac 2003-11-20 17:55:32 UTC
Triage->Easyfix

Comment 3 Elliot Lee 2003-12-17 19:45:35 UTC

*** This bug has been marked as a duplicate of 109498 ***

Comment 4 Red Hat Bugzilla 2006-02-21 19:00:02 UTC
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.