Bug 18133 - broken logging
broken logging
Status: CLOSED DUPLICATE of bug 17420
Product: Red Hat Linux
Classification: Retired
Component: mgetty (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Nalin Dahyabhai
Depends On:
  Show dependency treegraph
Reported: 2000-10-02 16:20 EDT by Enrico Scholz
Modified: 2008-05-01 11:37 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2000-10-02 16:20:32 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Enrico Scholz 2000-10-02 16:20:30 EDT
mgetty-1.1.22-1 has a bad logging-behavior because it outputs at
successful operations (loglevel L_MESG) the errno-string. An example
output is

| Sep 27 22:53:14 feldi mgetty[11711]: waiting...: No such file or

The reason lies in mgetty-1.1.22-excl.patch removing the parts of logfile.c
which are handling harmless messages. Now 

| syslog( level == L_FATAL? LOG_ALERT: LOG_ERR, "%s: %m", ws );

will be called also if level is L_MESG only.
Comment 1 Bill Nottingham 2000-10-02 18:27:32 EDT

*** This bug has been marked as a duplicate of 17420 ***

Note You need to log in before you can comment on or make changes to this bug.