1 .\" Hey Emacs! This file is -*- nroff -*- source.
3 .\" Copyright (c) Andrew G. Morgan 1996-7 <morgan@parc.power.net>
4 .TH PAM_START 3 "1997 Feb 15" "Linux-PAM 0.56" "Application Programmers' Manual"
7 pam_start, pam_end \- activating Linux-PAM
10 .B #include <security/pam_appl.h>
12 .BI "int pam_start(const char " *service ", const char " *user ", const struct pam_conv " *conv ", pam_handle_t " **pamh_p ");"
14 .BI "int pam_end(pam_handle_t " *pamh ", int " pam_status ");"
21 library. Identifying the application with a particular
27 if not known at the time the interface is initialized. The
28 conversation structure is passed to the library via the
30 argument. (For a complete description of this and other structures
31 the reader is directed to the more verbose
33 application developers' guide). Upon successful initialization, an
34 opaque pointer-handle for future access to the library is returned
35 through the contents of the
43 library. The service application associated with the
45 handle, is terminated. The argument,
47 passes the value most recently returned to the application from the
48 library; it indicates the manner in which the library should be
49 shutdown. Besides carrying a return value, this argument may be
52 to indicate that the module should not treat the call too
53 seriously. It is generally used to indicate that the current closing
54 of the library is in a
56 process, and that the parent will take care of cleaning up things that
57 exist outside of the current process space (files etc.).
69 May be translated to text with
70 .BR pam_strerror "(3). "
73 DCE-RFC 86.0, October 1995.
77 flag is pending acceptance with the DCE (as of 1996/12/4).
86 .BR pam_authenticate "(3), "
87 .BR pam_acct_mgmt "(3), "
88 .BR pam_open_session "(3), "
90 .BR pam_chauthtok "(3)."
95 .BR "System administrators" ", "
96 .BR "module developers" ", "
98 .BR "application developers" ". "