Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:
While trying to test bug #1113215, I have found that logger accepts 'kern' as facility name but the message gets logged under 'user'.

The manpage doesn't document this behaviour; in fact, there's a remark within the facility list saying "kern (can't be generated from user process)" from which I'd expect trying to use 'kern' should result in error.

Version-Release number of selected component (if applicable):
util-linux-2.23.2-21.el7.x86_64

How reproducible:
always

Steps to Reproduce:
1. logger -p kern.info test
2. echo $?

Actual results:
0

(the message gets logged)

Expected results:
ERROR: Cannot report to 'kern' facility from non-kernel process.
1

(the message doesn't get logged)

Additional info:
If the facility substitution is really that desirable (logger call must not end in error) or happens outside the control of logger and the culprit cannot be fixed then at least document this behaviour of the -p option. Also, in that case, printing at least a warning would be nice.

logger(1) does not substitute anything.

It's kernel (and libc) behaviour, you cannot inject kernel message from userspace.

All we can improve is docs (to make it more obvious) and maybe add a warning message.

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2015-2093.html