summaryrefslogtreecommitdiff
path: root/usr/src/man/man3pam/pam_sm_open_session.3pam
diff options
context:
space:
mode:
Diffstat (limited to 'usr/src/man/man3pam/pam_sm_open_session.3pam')
-rw-r--r--usr/src/man/man3pam/pam_sm_open_session.3pam8
1 files changed, 4 insertions, 4 deletions
diff --git a/usr/src/man/man3pam/pam_sm_open_session.3pam b/usr/src/man/man3pam/pam_sm_open_session.3pam
index 10d1814374..0245e0aef6 100644
--- a/usr/src/man/man3pam/pam_sm_open_session.3pam
+++ b/usr/src/man/man3pam/pam_sm_open_session.3pam
@@ -29,7 +29,7 @@ for pam_open_session and pam_close_session
In response to a call to \fBpam_open_session\fR(3PAM) and
\fBpam_close_session\fR(3PAM), the \fBPAM\fR framework calls
\fBpam_sm_open_session()\fR and \fBpam_sm_close_session()\fR, respectively from
-the modules listed in the \fBpam.conf\fR(4) file. The session management
+the modules listed in the \fBpam.conf\fR(5) file. The session management
provider supplies the back-end functionality for this interface function.
.sp
.LP
@@ -49,7 +49,7 @@ Session service should not generate any messages.
.sp
.LP
The \fIargc\fR argument represents the number of module options passed in from
-the configuration file \fBpam.conf\fR(4). \fIargv\fR specifies the module
+the configuration file \fBpam.conf\fR(5). \fIargv\fR specifies the module
options, which are interpreted and processed by the session management service.
If an unknown option is passed in, an error should be logged through
\fBsyslog\fR(3C) and the option ignored.
@@ -76,7 +76,7 @@ Ignore underlying session module regardless of whether the control flag is
.RE
.SH ATTRIBUTES
-See \fBattributes\fR(5) for description of the following attributes:
+See \fBattributes\fR(7) for description of the following attributes:
.sp
.sp
@@ -93,7 +93,7 @@ MT-Level MT-Safe with exceptions
.SH SEE ALSO
\fBpam\fR(3PAM), \fBpam_open_session\fR(3PAM), \fBsyslog\fR(3C),
-\fBlibpam\fR(3LIB), \fBpam.conf\fR(4), \fBattributes\fR(5)
+\fBlibpam\fR(3LIB), \fBpam.conf\fR(5), \fBattributes\fR(7)
.SH NOTES
The interfaces in \fBlibpam\fR are MT-Safe only if each thread within the
multithreaded application uses its own \fBPAM\fR handle.