Relevant BUGIDs: 812567

Purpose of commit: new feature

Commit summary:
---------------
Document new "include" directive for pam config file syntax.

2 files changed, 14 insertions, 2 deletions

diff --git a/doc/man/pam.8 b/doc/man/pam.8
index 939a0fe9..50fc9767 100644
--- a/doc/man/pam.8
+++ b/doc/man/pam.8
@@ -231,6 +231,12 @@ only module in the stack associated with this
 .BR service "+" type "."
 
 .sp
+New control directive first introduced in ALT Linux is
+.BR include
+- include all lines of given type from the configuration
+file specified as an argument to this control.
+
+.sp
 For the more complicated syntax valid
 .B control
 values have the following form:
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
-<tt/optional/.
+keywords: <tt/required/, <tt/requisite/, <tt/sufficient/,
+<tt/optional/ and <tt/include/.
 
 <p>
 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
 <tt/PAM_IGNORE/.
 
+<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.
+
+
 </itemize>
 
 <p>