filename -> file name like the rest of the docs
This commit is contained in:
8
INSTALL
8
INSTALL
@@ -180,22 +180,22 @@ Special features/options:
|
||||
containing the LDAP include and lib directories. Please see
|
||||
README.LDAP for more information.
|
||||
|
||||
--with-ldap-conf-file=filename
|
||||
--with-ldap-conf-file=PATH
|
||||
Path to LDAP configuration file. If specified, sudo reads
|
||||
this file instead of /etc/ldap.conf to locate the LDAP server.
|
||||
|
||||
--with-ldap-secret-file=filename
|
||||
--with-ldap-secret-file=PATH
|
||||
Path to LDAP secret password file. If specified, sudo uses
|
||||
this file instead of /etc/ldap.secret to read the secret password
|
||||
when rootbinddn is specified in the ldap config file.
|
||||
|
||||
--with-nsswitch[=filename]
|
||||
--with-nsswitch[=PATH]
|
||||
Path to nsswitch.conf or "no" to disable nsswitch support.
|
||||
If specified, sudo uses this file instead of /etc/nsswitch.conf.
|
||||
If nsswitch is disabled but LDAP is enabled, sudo will check
|
||||
LDAP first, then the sudoers file.
|
||||
|
||||
--with-netsvc[=filename]
|
||||
--with-netsvc[=PATH]
|
||||
Path to netsvc.conf or "no" to disable netsvc.conf support.
|
||||
If specified, sudo uses this file instead of /etc/netsvc.conf
|
||||
on AIX systems.
|
||||
|
@@ -151,8 +151,8 @@ Configure your /etc/ldap.conf and /etc/nsswitch.conf
|
||||
====================================================
|
||||
The /etc/ldap.conf file is meant to be shared between sudo, pam_ldap, nss_ldap
|
||||
and other ldap applications and modules. IBM Secureway unfortunately uses
|
||||
the same filename but has a different syntax. If you need to rename where
|
||||
this file is stored, re-run configure with the --with-ldap-conf-file=filename
|
||||
the same file name but has a different syntax. If you need to change where
|
||||
this file is stored, re-run configure with the --with-ldap-conf-file=PATH
|
||||
option.
|
||||
|
||||
See the "Configuring ldap.conf" section in the sudoers.ldap manual
|
||||
|
Reference in New Issue
Block a user