Relevant BUGIDs:

Purpose of commit: bugfix

Commit summary:
---------------

Fix typo.

diff --git a/modules/pam_unix/README b/modules/pam_unix/README
index 0caa313150b1b25bb5378d90dad9bbe753139219..3421eb3127462a64d5e7079d2e3a9a7bf89618ce 100644 (file)
--- a/modules/pam_unix/README
+++ b/modules/pam_unix/README
@@ -26,11 +26,11 @@ A helper binary, unix_chkpwd(8), is provided to check the user's password when
 it is stored in a read protected database. This binary is very simple and will
 only check the password of the user invoking it. It is called transparently on
 behalf of the user by the authenticating component of this module. In this way
-it is possible for applications like xlock to work without being setuid-root.
-The module, by default, will temporarily turn off SIGCHLD handling for the
-duration of execution of the helper binary. This is generally the right thing
-to do, as many applications are not prepared to handle this signal from a child
-they didn't know was fork()d. The noreap module argument can be used to
+it is possible for applications like xlock(1) to work without being
+setuid-root. The module, by default, will temporarily turn off SIGCHLD handling
+for the duration of execution of the helper binary. This is generally the right
+thing to do, as many applications are not prepared to handle this signal from a
+child they didn't know was fork()d. The noreap module argument can be used to
 suppress this temporary shielding and may be needed for use with certain
 applications.
 

diff --git a/modules/pam_unix/pam_unix.8 b/modules/pam_unix/pam_unix.8
index e7f11acdc790499225e6e8c9bf830115cecf0edd..e57de221fe26229b253cdf132ac478f3cd8fb4bc 100644 (file)
--- a/modules/pam_unix/pam_unix.8
+++ b/modules/pam_unix/pam_unix.8
@@ -33,7 +33,7 @@ The authentication component performs the task of checking the users credentials
 .PP
 A helper binary,
 \fBunix_chkpwd\fR(8), is provided to check the user's password when it is stored in a read protected database. This binary is very simple and will only check the password of the user invoking it. It is called transparently on behalf of the user by the authenticating component of this module. In this way it is possible for applications like
-\fBxlock\fR
+\fBxlock\fR(1)
 to work without being setuid\-root. The module, by default, will temporarily turn off SIGCHLD handling for the duration of execution of the helper binary. This is generally the right thing to do, as many applications are not prepared to handle this signal from a child they didn't know was
 \fBfork()\fRd. The
 \fBnoreap\fR

diff --git a/modules/pam_unix/pam_unix.8.xml b/modules/pam_unix/pam_unix.8.xml
index 25a705c18f62b76ae74ebe924bed059ee8ea8fad..417579778921744295096dd3189adba98e9c0598 100644 (file)
--- a/modules/pam_unix/pam_unix.8.xml
+++ b/modules/pam_unix/pam_unix.8.xml
@@ -67,7 +67,9 @@
       check the password of the user invoking it. It is called
       transparently on behalf of the user by the authenticating
       component of this module. In this way it is possible
-      for applications like <command>xlock</command> to work without
+      for applications like <citerefentry>
+      <refentrytitle>xlock</refentrytitle><manvolnum>1</manvolnum>
+      </citerefentry> to work without
       being setuid-root. The module, by default, will temporarily turn
       off SIGCHLD handling for the duration of execution of the helper
       binary. This is generally the right thing to do, as many applications