1
.\" Hey Emacs! This file is -*- nroff -*- source.
2
.\" $Id: pam_start.3,v 1.4 2002/09/21 18:19:20 hartmans Exp $
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"
6
pam_start, pam_end \- activating Linux-PAM
8
.B #include <security/pam_appl.h>
10
.BI "int pam_start(const char " *service ", const char " *user ", const struct pam_conv " *conv ", pam_handle_t " **pamh_p ");"
12
.BI "int pam_end(pam_handle_t " *pamh ", int " pam_status ");"
19
library. Identifying the application with a particular
25
if not known at the time the interface is initialized. The
26
conversation structure is passed to the library via the
28
argument. (For a complete description of this and other structures
29
the reader is directed to the more verbose
31
application developers' guide). Upon successful initialization, an
32
opaque pointer-handle for future access to the library is returned
33
through the contents of the
41
library. The service application associated with the
43
handle, is terminated. The argument,
45
passes the value most recently returned to the application from the
46
library; it indicates the manner in which the library should be
47
shutdown. Besides carrying a return value, this argument may be
50
to indicate that the module should not treat the call too
51
seriously. It is generally used to indicate that the current closing
52
of the library is in a
54
process, and that the parent will take care of cleaning up things that
55
exist outside of the current process space (files etc.).
67
May be translated to text with
68
.BR pam_strerror "(3). "
71
DCE-RFC 86.0, October 1995.
75
flag is pending acceptance with the DCE (as of 1996/12/4).
84
.BR pam_authenticate "(3), "
85
.BR pam_acct_mgmt "(3), "
86
.BR pam_open_session "(3), "
88
.BR pam_chauthtok "(3)."
93
.BR "System administrators" ", "
94
.BR "module developers" ", "
96
.BR "application developers" ". "