xref: /titanic_41/usr/src/man/man5/pam_unix_session.5 (revision 3e2514dc0f3dfbffad7bfb4744cf26707a910f26)
te
Copyright (C) 2002, Sun Microsystems, Inc.
All Rights Reserved
The contents of this file are subject to the terms of the Common Development and Distribution License (the "License"). You may not use this file except in compliance with the License.
You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE or http://www.opensolaris.org/os/licensing. See the License for the specific language governing permissions and limitations under the License.
When distributing Covered Code, include this CDDL HEADER in each file and include the License file at usr/src/OPENSOLARIS.LICENSE. If applicable, add the following below this CDDL HEADER, with the fields enclosed by brackets "[]" replaced with your own identifying information: Portions Copyright [yyyy] [name of copyright owner]
PAM_UNIX_SESSION 5 "Sep 9, 2004"
NAME
pam_unix_session - session management PAM module for UNIX
SYNOPSIS

pam_unix_session.so.1
DESCRIPTION

The pam_unix_session module implements pam_sm_open_session(3PAM) and pam_sm_close_session(3PAM).

pam_sm_open_session() updates the /var/adm/lastlog file with the information contained in the PAM_USER, PAM_TTY, and PAM_RHOSTS items. pam_unix_account(5) uses this account to determine the previous time the user logged in.

pam_sm_close_session() is a null function.

The following options can be passed to the module: debug

syslog(3C) debugging information at the LOG_DEBUG level

ERRORS

Upon successful completion, PAM_SUCCESS is returned. The following error codes are returned upon error: PAM_SESSION_ERR

Cannot make or remove the entry for the specified session (PAM_TTY is not present).

PAM_USER_UNKNOWN

No account is present for user.

ATTRIBUTES

See attributes(5) for descriptions of the following attributes:

ATTRIBUTE TYPE ATTRIBUTE VALUE
Interface Stability Evolving
MT Level MT-Safe with exceptions
SEE ALSO

pam(3PAM), pam_authenticate(3PAM), syslog(3C), libpam(3LIB), pam.conf(4), nsswitch.conf(4), attributes(5), pam_authtok_check(5), pam_authtok_get(5), pam_authtok_store(5), pam_dhkeys(5), pam_passwd_auth(5), pam_unix_account(5),pam_unix_auth(5),

NOTES

The interfaces in libpam(3LIB) are MT-Safe only if each thread within the multi-threaded application uses its own PAM handle.

The pam_unix(5) module is no longer supported. Similar functionality is provided by pam_authtok_check(5), pam_authtok_get(5), pam_authtok_store(5), pam_dhkeys(5), pam_passwd_auth(5), pam_unix_account(5), pam_unix_auth(5), and pam_unix_session(5).