libpam-chroot (0.9-4.1) TROUBLESHOOTING

Summary

 TROUBLESHOOTING |    6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

    
download this patch

Patch contents

--- libpam-chroot-0.9.orig/TROUBLESHOOTING
+++ libpam-chroot-0.9/TROUBLESHOOTING
@@ -6,7 +6,7 @@
 Note that all of the following assumes that you have put pam_chroot into
 debug mode (add the "debug" option to the pam_chroot line in the
 appropriate /etc/pam.d file) and that syslogd is configured to put
-auth.debug messages in some known location (/var/log/messages,
+auth.notice and auth.debug messages in some known location (/var/log/messages,
 /var/adm/messages, /var/adm/syslog/syslog.log, etc.)
 
 Under normal operation, pam_chroot will output something similar to the
@@ -42,8 +42,8 @@
   appropriate /etc/pam.d file, or it might be that PAM is not being used
   at all.  (For example, you might have set 'UsePAM no' in your
   /etc/ssh/sshd_config.)  It might also be that syslogd is not running or
-  is not configured to report auth.debug messages in the file that you're
-  looking for them in.
+  is not configured to report auth.notice and auth.debug messages in the 
+  file that you're looking for them in.
   There are a multitude of reasons that PAM might not be being used, and
   they're usually application configuration issues, rather than issues with
   PAM itself.