1 .\" ** You probably do not want to edit this file directly **
2 .\" It was generated using the DocBook XSL Stylesheets (version 1.69.1).
3 .\" Instead of manually editing it, you probably should edit the DocBook XML
4 .\" source for it and then use the DocBook XSL Stylesheets to regenerate it.
5 .TH "PAM_END" "3" "02/14/2006" "Linux\-PAM Manual" "Linux\-PAM Manual"
6 .\" disable hyphenation
8 .\" disable justification (adjust text to left margin only)
11 pam_end \- termination of PAM transaction
14 \fB#include <security/pam_appl.h>\fR
16 \fBint\ \fBpam_end\fR\fR\fB(\fR\fBpam_handle_t\ *\fR\fB\fIpamh\fR\fR\fB, \fR\fBint\ \fR\fB\fIpam_status\fR\fR\fB);\fR
21 function terminates the PAM transaction and is the last function an application should call in the PAM contenxt. Upon return the handle
23 is no longer valid and all memory associated with it will be invalid.
27 argument should be set to the value returned to the application by the last PAM library call.
31 is used as an argument to the module specific callback function,
36 \fBpam_get_data\fR(3)). In this way the module can be given notification of the pass/fail nature of the tear\-down process, and perform any last minute tasks that are appropriate to the module before it is unlinked. This argument can be logically OR'd with
38 to indicate to indicate that the module should not treat the call too seriously. It is generally used to indicate that the current closing of the library is in a
39 \fBfork\fR(2)ed process, and that the parent will take care of cleaning up things that exist outside of the current process space (files etc.).
42 \fIfree\fR's all memory for items associated with the
46 functions. Pointers associated with such objects are not valid anymore after
52 Transaction was successful terminated.
55 System error, for example a NULL pointer was submitted as PAM handle or the function was called by a module.
58 \fBpam_get_data\fR(3),
59 \fBpam_set_data\fR(3),