Bug 104035 - events getting ignored by syslgod
events getting ignored by syslgod
Status: CLOSED NOTABUG
Product: Red Hat Linux
Classification: Retired
Component: sysklogd (Show other bugs)
9
All Linux
medium Severity medium
: ---
: ---
Assigned To: Jason Vas Dias
Brian Brock
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2003-09-09 06:15 EDT by Bastien Nocera
Modified: 2007-04-18 12:57 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2004-08-04 19:42:07 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Bastien Nocera 2003-09-09 06:15:20 EDT
Add an entry at the top of /etc/syslogd.conf:
kern.*   /var/log/kernel

Restart syslog:
service syslog restart

logger -p kern.warn "Warning test"

The "Warning test" doesn't get logged in /var/log/kernel, although the file is
created. A "*.*" entry will log this message to /var/log/kernel fine.
Comment 1 Jason Vas Dias 2004-08-04 19:42:07 EDT
Messages generated by 
  logger -p kern.warn "Warning test"
are handled by syslogd as user messages and get logged to
/var/log/messages.

Genuine kernel messages, from the kernel, are handled by klogd
and 'kern.warn' messages would be redirected to /var/log/kernel
by 'kern.warn /var/log/kernel' in syslog.conf.

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