path: root/doc/pam_source.sgml
diff options
authorJan Rekorajski <>2003-09-25 17:49:29 +0000
committerJan Rekorajski <>2003-09-25 17:49:29 +0000
commit901333def6c893f5decdfd62178c6654915ae7fa (patch)
treeded312f1c3eae88bd3f51f0b378351d762770f83 /doc/pam_source.sgml
parent8e75c66582868ef647aa80f3d36c0985e0b394b8 (diff)
Relevant BUGIDs: 812567
Purpose of commit: new feature Commit summary: --------------- Document new "include" directive for pam config file syntax.
Diffstat (limited to 'doc/pam_source.sgml')
1 files changed, 8 insertions, 2 deletions
diff --git a/doc/pam_source.sgml b/doc/pam_source.sgml
index 674404b4..2ea9a7c9 100644
--- a/doc/pam_source.sgml
+++ b/doc/pam_source.sgml
@@ -437,8 +437,8 @@ with one of two syntaxes.
The simpler (and historical) syntax for the control-flag is a single
keyword defined to indicate the severity of concern associated with
the success or failure of a specific module. There are four such
-keywords: <tt/required/, <tt/requisite/, <tt/sufficient/ and
+keywords: <tt/required/, <tt/requisite/, <tt/sufficient/,
+<tt/optional/ and <tt/include/.
The Linux-PAM library interprets these keywords in the following
@@ -481,6 +481,12 @@ determine the nature of the response to the application. One example
of this latter case, is when the other modules return something like
+<item> <tt/include/; this tells PAM to include all lines of given type
+from the configuration file specified as an argument to this control.
+The whole idea is to create few "systemwide" pam configs and include
+parts of them in application pam configs.