Your message dated Mon, 20 Jan 2025 12:31:36 -0700 with message-id <[email protected]> and subject line Use quiet_log option has caused the Debian Bug report #781100, regarding libpam-modules: pam_exec.so quiet still logging errors to syslog to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 781100: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=781100 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: libpam-modules Version: 1.1.8-3.1 Severity: normal Dear Maintainer, I'm using pam_exec.so with the quiet option (/bin/false is just an example of a program with exit code 1): session [system_err=ignore default=1] pam_exec.so quiet /bin/false The man page says the following about quiet: quiet Per default pam_exec.so will echo the exit status of the external command if it fails. Specifying this option will suppress the message. However the following is still logged: Mar 24 14:34:32 host kdm: :1[4351]: pam_exec(kdm:session): /bin/false failed: exit code 1 I'd expect no error to be logged as mentioned in the man page. Regards Simon
--- End Message ---
--- Begin Message ---version: 1.5.2-1 The quiet option was never intended to suppress the syslog message. Instead, it suppressed a output to stderr of the PAM application (via a PAM_ERROR conversation item). Upstream commit bd76c538ef4747912733458a5d9e645424ea93fb added a quiet_log option to suppress the log message; this is included in Debian stable. --Sam
--- End Message ---
