path: root/doc/man/pam_start.3
diff options
Diffstat (limited to 'doc/man/pam_start.3')
1 files changed, 0 insertions, 80 deletions
diff --git a/doc/man/pam_start.3 b/doc/man/pam_start.3
deleted file mode 100644
index 22521213..00000000
--- a/doc/man/pam_start.3
+++ /dev/null
@@ -1,80 +0,0 @@
-.\" Title: pam_start
-.\" Author:
-.\" Generator: DocBook XSL Stylesheets v1.70.1 <>
-.\" Date: 06/27/2006
-.\" Manual: Linux\-PAM Manual
-.\" Source: Linux\-PAM Manual
-.TH "PAM_START" "3" "06/27/2006" "Linux\-PAM Manual" "Linux\-PAM Manual"
-.\" disable hyphenation
-.\" disable justification (adjust text to left margin only) l
-pam_start \- initialization of PAM transaction
-.ft B
-#include <security/pam_appl.h>
-.HP 14
-.BI "int pam_start(const\ char\ *" "service_name" ", const\ char\ *" "user" ", const\ struct\ pam_conv\ *" "pam_conversation" ", pam_handle_t\ **" "pamh" ");"
-function creates the PAM context and initiates the PAM transaction. It is the first of the PAM functions that needs to be called by an application. The transaction state is contained entirely within the structure identified by this handle, so it is possible to have multiple transactions in parallel. But it is not possible to use the same handle for different transactions, a new one is needed for every new context.
-argument specifies the name of the service to apply and will be stored as PAM_SERVICE item in the new context. The policy for the service will be read from the file
-or, if that file does not exist, from
-argument can specify the name of the target user and will be stored as PAM_USER item. If the argument is NULL, the module has to ask for this item if necessary.
-argument points to a
-\fIstruct pam_conv\fR
-describing the conversation function to use. An application must provide this for direct communication between a loaded module and the application.
-Following a successful return (PAM_SUCCESS) the contents of
-is a handle that contains the PAM context for successive calls to the PAM functions. In an error case is the content of
-is a blind structure and the application should not attempt to probe it directly for information. Instead the PAM library provides the functions
-\fBpam_get_item\fR(3). The PAM handle cannot be used for mulitiple authentications at the same time as long as
-was not called on it before.
-.TP 3n
-General failure.
-.TP 3n
-Memory buffer error.
-.TP 3n
-Transaction was successful created.
-.TP 3n
-System error, for example a NULL pointer was submitted instead of a pointer to data.