Bug 19889 - buggy syslogd config
Summary: buggy syslogd config
Keywords:
Status: CLOSED DUPLICATE of bug 18122
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: sysklogd
Version: 7.0
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Bill Nottingham
QA Contact: David Lawrence
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2000-10-27 00:48 UTC by Olivier Benghozi
Modified: 2014-03-17 02:17 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2000-10-27 22:45:17 UTC
Embargoed:


Attachments (Terms of Use)

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 ***


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