Bug 585533
Summary: | /usr/bin/logger silently redirects logging for "kern" facility to "user" facility | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 5 | Reporter: | David Tonhofer <bughunt> |
Component: | util-linux | Assignee: | Karel Zak <kzak> |
Status: | CLOSED NOTABUG | QA Contact: | qe-baseos-daemons |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | 5.7 | ||
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2010-04-26 07:05:25 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
David Tonhofer
2010-04-24 15:17:52 UTC
man 3 syslog: LOG_KERN kernel messages (these can’t be generated from user processes) Zut alors.
The Ubuntu manpage for syslog.conf is even more precise:
> 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
> implementation 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.
but in that case, would it be useful to
- add a corresponding remark to the manpage of the "logger" command
and/or
- make "logger" warn about messages directed to "kern" facility (might break
existing scripts though)
(In reply to comment #2) > Zut alors. > - add a corresponding remark to the manpage of the "logger" command Good point. Added to the upstream tree. Thanks. |