Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 19889

Summary: buggy syslogd config
Product: [Retired] Red Hat Linux Reporter: Olivier Benghozi <olivier.benghozi+redhatbugzilla>
Component: sysklogdAssignee: Bill Nottingham <notting>
Status: CLOSED DUPLICATE QA Contact: David Lawrence <dkl>
Severity: medium Docs Contact:
Priority: medium    
Version: 7.0CC: dr, rvokal
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: 2000-10-27 22:45:17 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 Olivier Benghozi 2000-10-27 00:48:00 UTC 
In RH 6.2, syslogd used to log CROND crontab jobs to /var/log/cron
and the rest to /var/log/messages.
in RH7, cron is still valid but messages is flooded by things that don't 
have their place in it: CROND entries are duplicated, once in cron, once 
in messages, with the same config than in 6.2.

If I use something like :
[blabla];cron.none	/var/log/messages

and the crontab line stays :
cron.*			/var/log/cron

then CROND messages are no longer logged anywhere.
According to the documentation of syslogd and syslogd.conf, this should be 
considered as a bug.
Comment 1 Bill Nottingham 2000-10-27 22:51:19 UTC 

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