Bug 14646 - pam_console emits debugging messages when debugging is not turned on
pam_console emits debugging messages when debugging is not turned on
Status: CLOSED DUPLICATE of bug 14644
Product: Red Hat Linux
Classification: Retired
Component: pam (Show other bugs)
6.2
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Nalin Dahyabhai
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2000-07-25 19:40 EDT by Chris Siebenmann
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:
Environment:
Last Closed: 2000-07-26 15:20:40 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
make the debugging messages actually debugging messages (703 bytes, patch)
2000-07-25 19:41 EDT, Chris Siebenmann
no flags Details | Diff

  None (edit)
Description Chris Siebenmann 2000-07-25 19:40:53 EDT
The new pam_console RPM emits debugging messages, messages about
perfectly normal and expected conditions, when the 'debug' argument
has not been specified to pam_console. The two immediately noticeable
(and annoying) messages are:
	console %s is owned by UID 0
and	console %s is a character device
These messages mean nothing more than that everything is OK. As such
they should only be emitted when debugging is turned on. Worse yet,
the code attempts to send them out at priority LOG_ERR, which should
be saved for things that indicate, well, important errors.

 I will attach a simple patch to fix this.
Comment 1 Chris Siebenmann 2000-07-25 19:41:25 EDT
Created attachment 1553 [details]
make the debugging messages actually debugging messages
Comment 2 Nalin Dahyabhai 2000-07-26 15:20:59 EDT

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

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