Whole document tree
6. Amd Configuration FileThe `amd.conf' file is the configuration file for Amd, as part of the am-utils suite. This file contains runtime configuration information for the Amd automounter program.
6.1 File FormatThe `amd.conf' file consists of sections and parameters. A section begins with the name of the section in square brackets `[]' and continues until the next section begins or the end of the file is reached. Sections contain parameters of the form `name = value'. The file is line-based -- that is, each newline-terminated line represents either a comment, a section name or a parameter. No line-continuation syntax is available. Section names, parameter names and their values are case sensitive. Only the first equals sign in a parameter is significant. Whitespace before or after the first equals sign is discarded. Leading, trailing and internal whitespace in section and parameter names is irrelevant. Leading and trailing whitespace in a parameter value is discarded. Internal whitespace within a parameter value is not allowed, unless the whole parameter value is quoted with double quotes as in `name = "some value"'. Any line beginning with a pound sign `#' is ignored, as are lines containing only whitespace. The values following the equals sign in parameters are all either a string (no quotes needed if string does not include spaces) or a boolean, which may be given as `yes'/`no'. Case is significant in all values. Some items such as cache timeouts are numeric.
6.2 The Global SectionThe global section must be specified as `[global]'. Parameters in this section either apply to Amd as a whole, or to all other regular map sections which follow. There should be only one global section defined in one configuration file. It is highly recommended that this section be specified first in the configuration file. If it is not, then regular map sections which precede it will not use global values defined later.
6.3 Regular Map SectionsParameters in regular (non-global) sections apply to a single map entry. For example, if the map section `[/homes]' is defined, then all parameters following it will be applied to the `/homes' Amd-managed mount point.
6.4 Common ParametersThese parameters can be specified either in the global or a map-specific section. Entries specified in a map-specific section override the default value or one defined in the global section. If such a common parameter is specified only in the global section, it is applicable to all regular map sections that follow.
6.4.1 browsable_dirs Parameter(type=string, default=`no'). If `yes', then Amd's top-level mount points will be browsable to readdir(3) calls. This means you could run for example ls(1) and see what keys are available to mount in that directory. Not all entries are made visible to readdir(3): the `/defaults' entry, wildcard entries, and those with a `/' in them are not included. If you specify `full' to this option, all but the `/defaults' entry will be visible. Note that if you run a command which will attempt to stat(2) the entries, such as often done by `ls -l' or `ls -F', Amd will attempt to mount every entry in that map. This is often called a "mount storm".
6.4.2 map_options Parameter(type=string, default no options). This option is the same as specifying map options on the command line to Amd, such as `cache:=all'.
6.4.3 map_type Parameter(type=string, default search all map types). If specified, Amd will initialize the map only for the type given. This is useful to avoid the default map search type used by Amd which takes longer and can have undesired side-effects such as initializing NIS even if not used. Possible values are
6.4.4 mount_type Parameter(type=string, default=`nfs'). All Amd mount types default to NFS. That is, Amd is an NFS server on the map mount points, for the local host it is running on. If `autofs' is specified, Amd will be an autofs server for those mount points.
6.4.5 search_path Parameter(type=string, default no search path). This provides a (colon-delimited) search path for file maps. Using a search path, sites can allow for local map customizations and overrides, and can distributed maps in several locations as needed.
6.5 Global ParametersThe following parameters are applicable to the `[global]' section only.
6.5.1 arch Parameter(type=string, default to compiled in value). Allows you to override the value of the arch Amd variable.
6.5.2 auto_dir Parameter
(type=string, default=`/a'). Same as the
6.5.3 cache_duration Parameter
(type=numeric, default=300). Same as the
6.5.4 cluster Parameter
(type=string, default no cluster). Same as the
6.5.5 debug_options Parameter
(type=string, default no debug options). Same as the
6.5.6 dismount_interval Parameter
(type=numeric, default=120). Same as the
6.5.7 full_os Parameter(type=string, default to compiled in value). The full name of the operating system, along with its version. Allows you to override the compiled-in full name and version of the operating system. Useful when the compiled-in name is not desired. For example, the full operating system name on linux comes up as `linux', but you can override it to `linux-2.2.5'.
6.5.8 fully_qualified_hosts Parameter(type=string, default=`no'). If `yes', Amd will perform RPC authentication using fully-qualified host names. This is necessary for some systems, and especially when performing cross-domain mounting. For this function to work, the Amd variable `${hostd}' is used, requiring that `${domain}' not be null.
6.5.9 hesiod_base Parameter(type=string, default=`automount'). Specify the base name for hesiod maps.
6.5.10 karch Parameter
(type=string, default to karch of the system). Same as the
6.5.11 ldap_base Parameter(type=string, default not set). Specify the base name for LDAP. This often includes LDAP-specific values such as country and organization.
6.5.12 ldap_cache_maxmem Parameter(type=numeric, default=131072). Specify the maximum memory Amd should use to cache LDAP entries.
6.5.13 ldap_cache_seconds Parameter(type=numeric, default=0). Specify the number of seconds to keep entries in the cache.
6.5.14 ldap_hostports Parameter(type=string, default not set). Specify the LDAP host and port values.
6.5.15 local_domain Parameter
(type=string, default no sub-domain). Same as the
6.5.16 log_file Parameter
(type=string, default=`stderr'). Same as the If the string `syslog' is given, Amd will record its events with the system logger syslogd(8). If your system supports syslog facilities, then the default facility used is `LOG_DAEMON'. When using syslog, if you wish to change the facility, append its name to the option name, delimited by a single colon. For example, if it is the string `syslog:local7' then Amd will log messages via syslog(3) using the `LOG_LOCAL7' facility. If the facility name specified is not recognized, Amd will default to `LOG_DAEMON'. Note: while you can use any syslog facility available on your system, it is generally a bad idea to use those reserved for other services such as `kern', `lpr', `cron', etc.
6.5.17 log_options Parameter
(type=string, default no logging options). Same as the
6.5.18 nfs_proto Parameter
(type=string, default to trying version tcp then udp). By default,
Amd tries
6.5.19 nfs_retransmit_counter Parameter
(type=numeric, default=11). Same as the retransmit part of the
6.5.20 nfs_retry_interval Parameter
(type=numeric, default=8). Same as the timeout part of the
Amd relies on the kernel RPC retransmit mechanism to trigger mount retries. The values of the nfs_retransmit_counter and the nfs_retry_interval parameters change the overall retry interval. Too long an interval gives poor interactive response; too short an interval causes excessive retries.
6.5.21 nfs_vers Parameter(type=numeric, default to trying version 3 then 2). By default, Amd tries version 3 and then version 2. This option forces the overall NFS protocol used to version 3 or 2. It overrides what is in the Amd maps, and is useful when Amd is compiled with NFSv3 support that may not be stable. With this option you can turn off the complete usage of NFSv3 dynamically (without having to recompile Amd) until such time as NFSv3 support is desired again.
6.5.22 nis_domain Parameter
(type=string, default to local NIS domain name). Same as the
6.5.23 normalize_hostnames Parameter
(type=boolean, default=`no'). Same as the
6.5.24 os Parameter
(type=string, default to compiled in value). Same as the
6.5.25 osver Parameter
(type=string, default to compiled in value). Same as the
6.5.26 pid_file Parameter
(type=string, default=`/dev/stdout'). Specify a file to store the process
ID of the running daemon into. If not specified, Amd will print its
process id onto the standard output. Useful for killing Amd after
it had run. Note that the PID of a running Amd can also be
retrieved via Amq (see section 7.4.7 Amq This file is used only if the `print_pid' option is on (see section 6.5.29 print_pid Parameter).
6.5.27 plock Parameter
(type=boolean, default=`yes'). Same as the
6.5.28 portmap_program Parameter
(type=numeric, default=300019). Specify an alternate Port-mapper RPC
program number, other than the official number. This is useful when
running multiple Amd processes. For example, you can run another
Amd in "test" mode, without affecting the primary Amd process
in any way. For safety reasons, the alternate program numbers that can
be specified must be in the range 300019-300029, inclusive. Amq has
an option
6.5.29 print_pid Parameter
(type=boolean, default=`no'). Same as the
6.5.30 print_version Parameter
(type=boolean, default=`no'). Same as the
6.5.31 restart_mounts Parameter
(type=boolean, default=`no'). Same as the
6.5.32 selectors_in_defaults Parameter(type=boolean, default=`no'). If `yes', then the `/defaults' entry of maps will search for and process any selectors before setting defaults for all other keys in that map. Useful when you want to set different options for a complete map based on some parameters. For example, you may want to better the NFS performance over slow slip-based networks as follows:
Deprecated form: selectors_on_default.
6.5.33 show_statfs_entries Parameter(type=boolean), default=`no'). If `yes', then all maps which are browsable will also show the number of entries (keys) they have when df(1) runs. (This is accomplished by returning non-zero values to the statfs(2) system call).
6.5.34 unmount_on_exit Parameter(type=boolean), default=`no'). If `yes', then Amd will attempt to unmount all file systems which it knows about. Normally it leaves all (esp. NFS) mounted file systems intact. Note that Amd does not know about file systems mounted before it starts up, unless the `restart_mounts' option is used (see section 6.5.31 restart_mounts Parameter).
6.5.35 vendor Parameter(type=string, default to compiled in value). The name of the vendor of the operating system. Overrides the compiled-in vendor name. Useful when the compiled-in name is not desired. For example, most Intel based systems set the vendor name to `unknown', but you can set it to `redhat'.
6.6 Regular Map ParametersThe following parameters are applicable only to regular map sections.
6.6.1 map_name Parameter(type=string, must be specified). Name of the map where the keys are located.
6.6.2 tag Parameter
(type=string, default no tag). Each map entry in the configuration file
can be tagged. If no tag is specified, that map section will always be
processed by Amd. If it is specified, then Amd will process the map
if the
6.7 amd.conf Examples
The following is the actual
This document was generated by Philippe Troin on March, 20 2002 using texi2html |