mirror of
https://github.com/linux-pam/linux-pam.git
synced 2024-11-23 09:43:36 +08:00
pam.conf: clarify default action for unspecified return codes
Add short blurbs explaining that if a return code is not specified in the "[value1=action1 value2=action2 ...]" form and "default=action" is not specified, that return code's action defaults to "bad". Signed-off-by: Jeff Squyres <jsquyres@cisco.com>
This commit is contained in:
parent
82288cd815
commit
d62120ed7c
@ -265,7 +265,8 @@
|
||||
this action indicates that the return code should be thought
|
||||
of as indicative of the module failing. If this module is the
|
||||
first in the stack to fail, its status value will be used for
|
||||
that of the whole stack.
|
||||
that of the whole stack. This is the default action for
|
||||
all return codes.
|
||||
</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
@ -335,6 +336,13 @@
|
||||
</varlistentry>
|
||||
</variablelist>
|
||||
|
||||
<para>
|
||||
If a return code's action is not specifically defined via a
|
||||
<emphasis>valueN</emphasis> token, and the
|
||||
<emphasis>default</emphasis> value is not specified, that return
|
||||
code's action defaults to <emphasis>bad</emphasis>.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
Each of the four keywords: required; requisite; sufficient; and
|
||||
optional, have an equivalent expression in terms of the [...]
|
||||
|
Loading…
Reference in New Issue
Block a user