[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#356844: marked as done (syslog(3) silently turns facility LOG_KERN to LOG_USER)

Your message dated Sun, 12 Jun 2011 15:04:35 +0200
with message-id <20110612130435.GA25099@volta.aurel32.net>
and subject line Re: sysklogd changes facility LOG_KERN to LOG_USER
has caused the Debian Bug report #356844,
regarding syslog(3) silently turns facility LOG_KERN to LOG_USER
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
356844: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=356844
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: sysklogd
Version: 1.4.1-17
Severity: normal

Hi there,

currently it's not possible to syslog(3) messages with facility LOG_KERN
with sysklogd,  It misinterprets LOG_KERN, which happens to be 0, with
no given facility and replaces it by LOG_USER.

BTW facility LOG_USER is default for logger(1) anyway.


Jürgen


-- System Information:
Debian Release: 3.1
Architecture: i386 (i686)
Kernel: Linux 2.6.14-2-k7
Locale: LANG=C, LC_CTYPE=de_DE@euro (charmap=ISO-8859-15)

Versions of packages sysklogd depends on:
ii  klogd [linux-kernel-log-dae 1.4.1-17     Kernel Logging Daemon
ii  libc6                       2.3.2.ds1-22 GNU C Library: Shared libraries an

-- no debconf information

--- End Message ---
--- Begin Message --- 
On Tue, Mar 14, 2006 at 01:57:48PM +0100, Jürgen E. Fischer wrote:
> Package: sysklogd
> Version: 1.4.1-17
> Severity: normal
> 
> Hi there,
> 
> currently it's not possible to syslog(3) messages with facility LOG_KERN
> with sysklogd,  It misinterprets LOG_KERN, which happens to be 0, with
> no given facility and replaces it by LOG_USER.
> 
> BTW facility LOG_USER is default for logger(1) anyway.
> 

LOG_KERN is reserved for the kernel and can't be sent from user
processes. That's why it's not a problem if LOG_KERN is equal to 0.
syslog(3) interpret the 0 value as the default facility, as specified in
POSIX2008.

The fact that LOG_KERN is reserved for the kernel is mentioned in the
documentation (info page and manpage), so there is clearly no bug there.
I am therefore closing it.

-- 
Aurelien Jarno                          GPG: 1024D/F1BCDB73
aurelien@aurel32.net                 http://www.aurel32.net

--- End Message ---
Reply to: