Imported Upstream version 1.8.5

[debian/sudo] / doc / sudoers.ldap.cat

diff --git a/doc/sudoers.ldap.cat b/doc/sudoers.ldap.cat
index fcbc56a03d0af998d48630125d805ddaf709a3f3..67d6d863f26f6c30b4377c50b502c2cdb5c02167 100644 (file)
--- a/doc/sudoers.ldap.cat
+++ b/doc/sudoers.ldap.cat
@@ -12,25 +12,25 @@ D\bDE\bES\bSC\bCR\bRI\bIP\bPT\bTI\bIO\bON\bN
 
        Using LDAP for _\bs_\bu_\bd_\bo_\be_\br_\bs has several benefits:
 
 
        Using LDAP for _\bs_\bu_\bd_\bo_\be_\br_\bs has several benefits:
 

-       +\bo   s\bsu\bud\bdo\bo no longer needs to read _\bs_\bu_\bd_\bo_\be_\br_\bs in its entirety.  When LDAP is
+       o   s\bsu\bud\bdo\bo no longer needs to read _\bs_\bu_\bd_\bo_\be_\br_\bs in its entirety.  When LDAP is

            used, there are only two or three LDAP queries per invocation.
            This makes it especially fast and particularly usable in LDAP
            environments.
 
            used, there are only two or three LDAP queries per invocation.
            This makes it especially fast and particularly usable in LDAP
            environments.
 

-       +\bo   s\bsu\bud\bdo\bo no longer exits if there is a typo in _\bs_\bu_\bd_\bo_\be_\br_\bs.  It is not
+       o   s\bsu\bud\bdo\bo no longer exits if there is a typo in _\bs_\bu_\bd_\bo_\be_\br_\bs.  It is not

            possible to load LDAP data into the server that does not conform to
            the sudoers schema, so proper syntax is guaranteed.  It is still
            possible to have typos in a user or host name, but this will not
            prevent s\bsu\bud\bdo\bo from running.
 
            possible to load LDAP data into the server that does not conform to
            the sudoers schema, so proper syntax is guaranteed.  It is still
            possible to have typos in a user or host name, but this will not
            prevent s\bsu\bud\bdo\bo from running.
 

-       +\bo   It is possible to specify per-entry options that override the
+       o   It is possible to specify per-entry options that override the

            global default options.  _\b/_\be_\bt_\bc_\b/_\bs_\bu_\bd_\bo_\be_\br_\bs only supports default options
            and limited options associated with user/host/commands/aliases.
            The syntax is complicated and can be difficult for users to
            understand.  Placing the options directly in the entry is more
            natural.
 
            global default options.  _\b/_\be_\bt_\bc_\b/_\bs_\bu_\bd_\bo_\be_\br_\bs only supports default options
            and limited options associated with user/host/commands/aliases.
            The syntax is complicated and can be difficult for users to
            understand.  Placing the options directly in the entry is more
            natural.
 

-       +\bo   The v\bvi\bis\bsu\bud\bdo\bo program is no longer needed.  v\bvi\bis\bsu\bud\bdo\bo provides locking
+       o   The v\bvi\bis\bsu\bud\bdo\bo program is no longer needed.  v\bvi\bis\bsu\bud\bdo\bo provides locking

            and syntax checking of the _\b/_\be_\bt_\bc_\b/_\bs_\bu_\bd_\bo_\be_\br_\bs file.  Since LDAP updates
            are atomic, locking is no longer necessary.  Because syntax is
            checked when the data is inserted into LDAP, there is no need for a
            and syntax checking of the _\b/_\be_\bt_\bc_\b/_\bs_\bu_\bd_\bo_\be_\br_\bs file.  Since LDAP updates
            are atomic, locking is no longer necessary.  Because syntax is
            checked when the data is inserted into LDAP, there is no need for a


@@ -747,4 +747,4 @@ D\bDI\bIS\bSC\bCL\bLA\bAI\bIM\bME\bER\bR
 
 
 
 
 
 

-1.8.4                          January  6, 2012                SUDOERS.LDAP(4)
+1.8.5                           March 14, 2012                 SUDOERS.LDAP(4)