Hi,
I came across this bug linked from
<https://bugs.launchpad.net/ubuntu/intrepid/+source/sysklogd/+bug/255635>,
since someone believed they were the same bug (they are not).
The reason you're finding that this doesn't work with logger is explained by
the following note in the syslog.conf(5) manpage:
In most cases anyone can log to any facility, so we rely on convention
for the correct facility to be chosen. However, generally only the
kernel can log to the "kern" facility. This is because the implementa‐
tion of openlog() and syslog() in glibc does not allow logging to the
"kern" facility. Klogd circumvents this restriction when logging to
syslogd by reimplementing those functions itself.
So this is a "bug" in logger or glibc only; I think it should probably just
be closed.
Cheers,
--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
Ubuntu Developer http://www.debian.org/
[EMAIL PROTECTED] [EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
