This is the mail archive of the
glibc-bugs@sourceware.org
mailing list for the glibc project.
[Bug libc/3604] New: syslog: messages meant for LOG_KERN go to LOG_USER
- From: "et at tallmaple dot com" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sources dot redhat dot com
- Date: 28 Nov 2006 02:54:12 -0000
- Subject: [Bug libc/3604] New: syslog: messages meant for LOG_KERN go to LOG_USER
- Reply-to: sourceware-bugzilla at sourceware dot org
If you call openlog() with LOG_KERN as the facility, it treats this as not
specifying a facility at all, and defaults to LOG_USER. Thus there is no way to
get anything logged in the 'kern' facility. The kernel is no exception, as
klogd simply calls openlog() with LOG_KERN like any other userland process.
I observed this on FC4 (glibc 2.3.6-3) but verified it looking at the latest
syslog.c and sys/syslog.h (1.49 and 1.17) in the CVS web access. LOG_KERN is
defined to be 0, but on line 341 of syslog.c, we ignore any facility of 0 passed
to openlog(), so the default of LOG_USER, assigned on line 70, is kept.
Similarly, on lines 164-165, we see that a facility of 0 is considered "not
specified".
--
Summary: syslog: messages meant for LOG_KERN go to LOG_USER
Product: glibc
Version: 2.3.6
Status: NEW
Severity: normal
Priority: P2
Component: libc
AssignedTo: drepper at redhat dot com
ReportedBy: et at tallmaple dot com
CC: glibc-bugs at sources dot redhat dot com
http://sourceware.org/bugzilla/show_bug.cgi?id=3604
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.