From 901333def6c893f5decdfd62178c6654915ae7fa Mon Sep 17 00:00:00 2001 From: Jan Rekorajski Date: Thu, 25 Sep 2003 17:49:29 +0000 Subject: Relevant BUGIDs: 812567 Purpose of commit: new feature Commit summary: --------------- Document new "include" directive for pam config file syntax. --- doc/man/pam.8 | 6 ++++++ doc/pam_source.sgml | 10 ++++++++-- 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 @@ -230,6 +230,12 @@ module has failed the success of this one is 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 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: 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

-- cgit v1.2.3