конфигурация autofs (autofs configuration)
SECTION autofs CONFIGURATION OPTIONS
Configuration settings available are:
timeout
Sets the default mount timeout in seconds. The internal
program default is 10 minutes, but the default installed
configuration overrides this and sets the timeout to 5
minutes to be consistent with earlier autofs releases.
master_wait
Sets the default maximum number of retries (actaul
iterations is half this, each is delayed by 2 seconds
before retrying) waiting for the master map to become
available if it cannot be read at program start (program
default 10, then continue). This can be longer if the map
source itself waits for availability (such as sss).
negative_timeout
Set the default timeout for caching failed key lookups
(program default 60). If the equivalent command line
option is given it will override this setting.
mount_verbose
Use the verbose flag when spawning mount(8), and log some
process info about the requestor and its parent (program
default "no").
mount_wait
Set the default time to wait for a response from a spawned
mount(8) before sending it a SIGTERM. Note that we still
need to wait for the RPC layer to timeout before the sub-
process exits so this isn't ideal but it is the best we
can do. The default is to wait until mount(8) returns
without intervention.
umount_wait
Set the default time to wait for a response from a spawned
umount(8) before sending it a SIGTERM. Note that we still
need to wait for the RPC layer to timeout before the sub-
process exits so this isn't ideal but it is the best we
can do.
browse_mode
Maps are browsable by default (program default "yes").
mount_nfs_default_protocol
Set the default protocol that mount.nfs(8) uses when
performing a mount (program default 3). Autofs needs to
know the default NFS protocol that mount.nfs(8) uses so it
can do special case handling for its availability probe
for different NFS protocols. Since we can't identify this
default automatically we need to set it in the autofs
configuration.
append_options
Determine whether global options, given on the command
line or per mount in the master map, are appended to map
entry options or if the map entry options replace the
global options (program default "yes", append options).
logging
set default log level "none", "verbose" or "debug"
(program default "none").
force_standard_program_map_env
override the use of a prefix with standard environment
variables when a program map is executed. Since program
maps are run as the privileged user setting these standard
environment variables opens automount(8) to potential user
privilege escalation when the program map is written in a
language that can load components from, for example, a
user home directory (program default "no").
map_hash_table_size
This configuration option may be used to change the number
of hash table slots (default 1024).
This configuration option affects the overhead of
searching the map entry cache for map entries when there
are a large number of entries. It affects the number of
entries that must be looked at to locate a map entry in
the map entry cache. For example, the default of 1024 and
a direct map with 8000 entries would result in each slot
containing an average of 8 entries, which should be
acceptable.
However, if excessive CPU usage is observed during
automount lookups increasing this option can reduce the
CPU overhead considerably because it reduces the length of
the search chains.
Note that the number of entries in a map doesn't
necessarily relate to the number of entries used in the
map entry cache.
There are two distinct cases where the map hash table can
make a significant difference, direct maps and indirect
maps that use the "browse" option.
For indirect maps that do not use the "browse" option
entries are added to the map entry cache at lookup so the
number of active cache entries, in this case, is usually
much less than the number of entries in the map. In this
last case it would be unusual for the map entry cache to
grow large enough to warrant increasing the default before
an event that cleans stale entries, a map re-read for
example.
use_hostname_for_mounts
NFS mounts where the host name resolves to more than one
IP address are probed for availability and to establish
the order in which mounts to them should be tried. To
ensure that mount attempts are made only to hosts that are
responding and are tried in the order of hosts with the
quickest response the IP address of the host needs to be
used for the mount.
If it is necessary to use the hostname given in the map
entry for the mount regardless, then set this option to
"yes".
Be aware that if this is done there is no defense against
the host name resolving to one that isn't responding and
while the number of attempts at a successful mount will
correspond to the number of addresses the host name
resolves to the order will also not correspond to fastest
responding hosts.
disable_not_found_message
The original request to add this log message needed it to
be unconditional. That produces, IMHO, unnecessary noise
in the log so a configuration option has been added to
provide the ability to turn it off. The default is "no" to
maintain the current behaviour.
use_ignore_mount_option
An option to enable the use of autofs pseudo option
"disable". This option is used as a hint to user space
that the mount entry should be ommitted from mount table
listings. The default is "no" to avoid unexpected changes
in behaviour and so is an opt-in setting.
sss_master_map_wait
Set the time to wait and retry if sssd is unable to read
the master map at program start. Program default is 0
(don't wait) or 10 if sss supports returning EHSTDOWN when
the provider isn't available.
If the sss library supports returning EHOSTDOWN when the
provider is down then this value is how long to wait
between retries reading the master map. When reading
dependent maps or looking up a map key this value is
multiplied by the number of retries that would be used
when reading the master map.
use_mount_request_log_id
Set whether to use a mount request log id so that log
entries for specific mount requests can be easily
identified in logs that have multiple concurrent requests.
Default is don't use mount request log ids.
LDAP Configuration
Configuration settings available are:
ldap_timeout
Set the network response timeout (default 8). Set timeout
value for the synchronous API calls. The default is the
LDAP library default of an infinite timeout.
ldap_network_timeout
Set the network response timeout (default 8).
ldap_uri
A space separated list of server uris of the form
<proto>://<server>[/] where <proto> can be ldap or ldaps.
The option can be given multiple times. Map entries that
include a server name override this option and it is then
not used. Default is an empty list in which case either
the server given in a map entry or the LDAP configured
default is used. This uri list is read at startup and
whenever the daemon receives a HUP signal.
This configuration option can also be used to request
autofs lookup SRV RRs for a domain of the form
<proto>:///[<domain dn>]. Note that a trailing "/" is not
allowed when using this form. If the domain dn is not
specified the dns domain name (if any) is used to
construct the domain dn for the SRV RR lookup. The server
list returned from an SRV RR lookup is refreshed according
to the minimum ttl found in the SRV RR records or after
one hour, whichever is less.
search_base
The base dn to use when searching for amap base dn. This
entry may be given multiple times and each will be checked
for a map base dn in the order they occur in the
configuration. The search base list is read at startup and
whenever the daemon recieves a HUP signal.
map_object_class
The map object class. In the nisMap schema this
corresponds to the class nisMap and in the automountMap
schema it corresponds to the class automountMap.
entry_object_class
The map entry object class. In the nisMap schema this
corresponds to the class nisObject and in the automountMap
schema it corresponds to the class automount.
map_attribute
The attribute used to identify the name of the map to
which this entry belongs. In the nisMap schema this
corresponds to the attribute nisMapName and in the
automountMap schema it corresponds to the attribute ou or
automountMapName.
entry_attribute
The attribute used to identify a map key. In the nisMap
schema this corresponds to the attribute cn and in the
automountMap schema it corresponds to the attribute
automountKey.
value_attribute
The attribute used to identify the value of the map entry.
In the nisMap schema this corresponds to the attribute
nisMapEntry and in the automountMap schema it corresponds
to the attribute automountInformation.
NOTE: It is essential that entries use class and attribute in a
consistent manner for correct operation of autofs. For
example mixing cn and automountKey attributes in automount
schema will not work as expected.
auth_conf_file
This configuration option may be used to specify an
alternate location for the ldap authentication
configuration file. See autofs_ldap_auth.conf(5) for more
information.
