Relevant BUGIDs:

[linux-pam] / doc / modules / pam_deny.sgml

diff --git a/doc/modules/pam_deny.sgml b/doc/modules/pam_deny.sgml
index 6e1f2992ee1cddb1581d986dd2a4f2a28e2a6259..6953231f21a6f44855f53496876b1bc316ff493d 100644 (file)
--- a/doc/modules/pam_deny.sgml
+++ b/doc/modules/pam_deny.sgml
@@ -1,7 +1,7 @@
 <!--
    $Id$
    
-   This file was written by Andrew G. Morgan <morgan@parc.power.net>
+   This file was written by Andrew G. Morgan <morgan@kernel.org>
 -->
 
 <sect1>The locking-out module
@@ -15,7 +15,7 @@
 pam_deny
 
 <tag><bf>Author:</bf></tag>
-Andrew G. Morgan &lt;morgan@parc.power.net&gt;
+Andrew G. Morgan &lt;morgan@kernel.org&gt;
 
 <tag><bf>Maintainer:</bf></tag>
 current <bf/Linux-PAM/ maintainer
@@ -155,11 +155,9 @@ session on the host computer.
 <tag><bf>Examples/suggested usage:</bf></tag>
 
 Together with another session module, that displays a message of the
-day perhaps (XXX - such a module needs to be written),
-this module can be used to block a user from starting a shell. Given
-the presence of a <tt/pam_motd/ module, we might use the following
-entries in the configuration file to inform the user it is system
-time:
+day perhaps (<tt/pam_motd/ for example), this module can be used to
+block a user from starting a shell. We might use the following entries
+in the configuration file to inform the user it is system time:
 <tscreen>
 <verb>
 #
@@ -167,7 +165,7 @@ time:
 # session (politely)
 #
 login  session  required       pam_motd.so \
-                       file=/etc/system_time
+                       motd=/etc/system_time
 login  session  required       pam_deny.so
 </verb>
 </tscreen>