summaryrefslogtreecommitdiff
path: root/modules/pam_unix
diff options
context:
space:
mode:
Diffstat (limited to 'modules/pam_unix')
-rw-r--r--modules/pam_unix/README10
-rw-r--r--modules/pam_unix/pam_unix.82
-rw-r--r--modules/pam_unix/pam_unix.8.xml4
3 files changed, 9 insertions, 7 deletions
diff --git a/modules/pam_unix/README b/modules/pam_unix/README
index 0caa3131..3421eb31 100644
--- 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 e7f11acd..e57de221 100644
--- 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 25a705c1..41757977 100644
--- 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