path: root/doc/man/pam_start.3.xml
diff options
authorThorsten Kukuk <>2006-05-04 06:56:04 +0000
committerThorsten Kukuk <>2006-05-04 06:56:04 +0000
commit7a31a6a26d87d1061580a7466869b28ac728ddd4 (patch)
tree2654f30e3f8ca026c56131bd1ee3c84276f0d255 /doc/man/pam_start.3.xml
parent20bf460d3e1a33ffd1e86510cc6f2ab50729cc40 (diff)
Relevant BUGIDs:
Purpose of commit: new feature, cleanup Commit summary: --------------- To unify look of error messages remove trailing dot from 4 pam_strerror() messages and adjust translations. Convert all xml files to UTF-8. Add pam.3 and pam_sm_acct_mgmt.3. 2006-05-04 Thorsten Kukuk <> * libpam/pam_strerror.c: Unify error messages. * po/zh_TW.po: Adjust for last pam_strerror changes. * po/zh_CN.po: Likewise. * po/uk.po: Likewise. * po/tr.po: Likewise. * po/pt.po: Likewise. * po/pt_BR.po: Likewise. * po/pl.po: Likewise. * po/ja.po: Likewise. * po/nl.po: Likewise. * po/nb.po: Likewise. * po/it.po: Likewise. * po/hu.po: Likewise. * po/fr.po: Likewise. * po/fi.po: Likewise. * po/es.po: Likewise. * po/de.po: Likewise. * po/cs.po: Likewise. * doc/man/pam.3.xml: New. * doc/man/pam.3. New, generated from XML file. * doc/man/pam_sm_acct_mgmt.3.xml: New. * doc/man/pam_sm_acct_mgmt.3: New, generated from XML file. * doc/man/*.xml: Fix encoding and use always UTF-8, regenerate all manual pages. * doc/pam_modules.sgml (PAM_NEW_AUTHTOKEN_REQD): Fix typo.
Diffstat (limited to 'doc/man/pam_start.3.xml')
1 files changed, 6 insertions, 2 deletions
diff --git a/doc/man/pam_start.3.xml b/doc/man/pam_start.3.xml
index 2850b15d..4ffd81a4 100644
--- a/doc/man/pam_start.3.xml
+++ b/doc/man/pam_start.3.xml
@@ -1,4 +1,4 @@
-<?xml version="1.0" encoding="ISO-8859-1"?>
+<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook XML V4.1.2//EN"
@@ -36,7 +36,11 @@
The <function>pam_start</function> 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.
+ 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.