1AUTO.MASTER(5) File Formats Manual AUTO.MASTER(5)
2
6 auto.master - Master Map for automounter
7
9 The auto.master map is consulted to set up automount managed mount
10 points when the autofs(8) script is invoked or the automount(8) program
11 is run. Each line describes a mount point and refers to an autofs map
12 describing file systems to be mounted under the mount point.
13 The default location of the master map is /etc/auto.master but an al‐
15 ternate name may be given on the command line when running the auto‐
16 mounter and the default master map may changed by setting the
17 MASTER_MAP_NAME configuration variable in /etc/sysconfig/autofs. If
18 the master map name has no path then the system Name Service Switch
19 configuration will be consulted and each of the sources searched in
20 line with the rules given in the Name Service Switch configuration.
21 Access to mounts in maps is governed by a key.
23 For direct maps the mount point is always specified as:
25 /-
27 and the key used within the direct map is the full path to the mount
29 point. The direct map may have multiple entries in the master map.
30 For indirect maps access is by using the path scheme:
32 /mount-point/key
34 where mount-point is one of the entries listed in the master map. The
36 key is a single directory component and is matched against entries in
37 the map given in the entry (See autofs(5)).
38 Additionally, a map may be included from its source as if it were it‐
40 self present in the master map by including a line of the form:
41 +[maptype[,format]:]map [options]
43 and automount(8) will process the map according to the specification
45 described below for map entries. Indirect map entries must be unique in
46 the master map so second and subsequent entries for an indirect mount
47 point are ignored by automount(8).
48
50 Master map entries have three fields separated by an arbitrary number
51 of spaces or tabs. Lines beginning with # are comments. The first field
52 is the mount point described above and the second field is the name of
53 the map to be consulted for the mount point followed by the third field
54 which contains options to be applied to all entries in the map.
55 The format of a master map entry is:
57 mount-point [map-type[,format]:]map [options]
59 mount-point
61 Base location for the autofs filesystem to be mounted. For in‐
62 direct maps this directory will be created (as with mkdir -p)
63 and is removed when the autofs filesystem is umounted.
64 map-type
66 Type of map used for this mount point. The following are valid
67 map types:
68 file The map is a regular text file.
70 program
72 The map is an executable program, which is passed a key
73 on the command line and returns an entry (everything be‐
74 sides the key) on stdout if successful. Optinally, the
75 keyword exec may be used as a synonym for program to
76 avoid confusion with amd formated maps mount type pro‐
77 gram.
78 yp The map is a NIS (YP) database.
80 nisplus
82 The map is a NIS+ database.
83 hesiod The map is a hesiod database whose filsys entries are
85 used for maps.
86 ldap or ldaps
88 The map is stored in an LDAP directory. If ldaps is used
89 the appropriate certificate must be configured in the
90 LDAP client.
91 multi This map type allows the specification of multiple maps
93 separated by "--". These maps are searched in order to
94 resolve key lookups.
95 format
97 Format of the map data; currently the formats recognized are
98 sun, which is a subset of the Sun automounter map format, hes‐
99 iod, for hesiod filesys entries and amd for amd formated map en‐
100 tries. If the format is left unspecified, it defaults to sun
101 for all map types except hesiod unless it is a top level amd
102 mount that has a configuration entry for the mount point path,
103 in which case the format used is amd.
104 map
106 Name of the map to use. This is an absolute UNIX pathname for
107 maps of types file or program, and the name of a database in the
108 case for maps of type yp, nisplus, or hesiod or the dn of an
109 LDAP entry for maps of type ldap.
110 options
112 Any remaining command line arguments without leading dashes (-)
113 are taken as options (-o) to mount. Arguments with leading
114 dashes are considered options for the maps and are passed to au‐
115 tomount (8).
116 The sun format supports the following options:
118 -Dvariable=value
120 Replace variable with value in map substitutions.
121 -strict
123 Treat errors when mounting file systems as fatal. This is
124 important when multiple file systems should be mounted
125 (`multimounts'). If this option is given, no file system
126 is mounted at all if at least one file system can't be
127 mounted.
128 [no]browse
130 This is an autofs specific option that is a pseudo mount
131 option and so is given without a leading dash. Use of the
132 browse option pre-creates mount point directories for in‐
133 direct mount maps so the map keys can be seen in a direc‐
134 tory listing without being mounted. Use of this option
135 can cause performance problem if the indirect map is
136 large so it should be used with caution. The internal
137 program default is to enable browse mode for indirect
138 mounts but the default installed configuration overrides
139 this by setting BROWSE_MODE to "no" because of the poten‐
140 tial performance problem.
141 nobind This is an autofs specific option that is a pseudo mount
143 option and so is given without a leading dash. It may be
144 used either in the master map entry (so it effects all
145 the map entries) or with individual map entries to pre‐
146 vent bind mounting of local NFS filesystems. For direct
147 mount maps the option is only effective if specified on
148 the first direct map entry and is applied to all direct
149 mount maps in the master map. It is ignored if given on
150 subsequent direct map entries. It may be used on individ‐
151 ual map entries of both types. Bind mounting of NFS file
152 systems can also be prevented for specific map entrys by
153 adding the "port=" mount option to the entries.
154 symlink
156 This option makes bind mounting use a symlink instead of
157 an actual bind mount. It is an autofs specific option
158 that is a pseudo mount option and so is given without a
159 leading dash. It may be used with indirect map entries
160 only, either in the master map (so it effects all map en‐
161 tries) or with individual map entries. The option is ig‐
162 nored for direct mounts and non-root offest mount en‐
163 tries.
164 -r, --random-multimount-selection
166 Enables the use of ramdom selection when choosing a host
167 from a list of replicated servers. This option is applied
168 to this mount only, overriding the global setting that
169 may be specified on the command line.
170 -w, --use-weight-only
172 Use only specified weights for server selection where
173 more than one server is specified in the map entry. If no
174 server weights are given then each available server will
175 be tried in the order listed, within proximity.
176 -t, --timeout <seconds>
178 Set the expire timeout for map entries. This option can
179 be used to override the global default given either on
180 the command line or in the configuration.
181 -n, --negative-timeout <seconds>
183 Set the timeout for caching failed key lookups. This op‐
184 tion can be used to override the global default given ei‐
185 ther on the command line or in the configuration.
186
188 If "-hosts" is given as the map then accessing a key under the mount
189 point which corresponds to a hostname will allow access to the exports
190 of that host. The hosts map cannot be dynamically updated and requires
191 a HUP signal to be sent to the daemon for it to check hosts for an up‐
192 date. Due to possible hierarchic dependencies within a mount tree, it
193 might not be completely updated during the HUP signal processing.
194 For example, with an entry in the master map of /net -hosts accessing
196 /net/myserver will mount exports from myserver on directories below
197 /net/myserver.
198 NOTE: mounts done from a hosts map will be mounted with the "no‐
200 suid,nodev,intr" options unless overridden by explicily specifying the
201 "suid", "dev" or "nointr" options in the master map entry.
202
204 If the map type ldap is specified the mapname is of the form [//server‐
205 name/]dn, where the optional servername is the name of the LDAP server
206 to query, and dn is the Distinguished Name of a subtree to search for
207 map entries. The old style ldap:servername:mapname is also understood.
208 Alternatively, the type can be obtained from the Name Service Switch
209 configuration, in which case the map name alone must be given.
210 If no schema is set in the autofs configuration then autofs will check
212 each of the commonly used schema for a valid entry and if one is found
213 it will used for subsequent lookups.
214 There are three common schemas in use:
216 nisMap
218 Entries in the nisMap schema are nisObject objects in the speci‐
219 fied subtree, where the cn attribute is the key (the wildcard
220 key is "/"), and the nisMapEntry attribute contains the informa‐
221 tion used by the automounter.
222 automountMap
224 The automountMap schema has two variations that differ in the
225 attribute used for the map key. Entries in the automountMap
226 schema are automount objects in the specified subtree, where the
227 cn or automountKey attribute (depending on local usage) is the
228 key (the wildcard key is "/"), and the automountInformation at‐
229 tribute contains the information used by the automounter. Note
230 that the cn attribute is case insensitive.
231 The object classes and attributes used for accessing automount maps in
233 LDAP can be changed by setting entries in the autofs configuration lo‐
234 cated in /etc/sysconfig/autofs.conf.
235 NOTE: If a schema is given in the configuration then all the schema
237 configuration values must be set, any partial schema specifica‐
238 tion will be ignored.
239 For amd format maps a different schema is used:
241 amdMap
243 The amdmap schema contains attributes amdmapName, amdmapKey and
244 amdmapValue where amdmapName contains the name of the containing
245 map, amdmapKey contains the map key and amdmapValue contains the
246 map entry.
247
249 LDAP authenticated binds, TLS encrypted connections and certification
250 may be used by setting appropriate values in the autofs authentication
251 configuration file and configuring the LDAP client with appropriate
252 settings. The default location of this file is
253 /etc/autofs_ldap_auth.conf.
254 If this file exists it will be used to establish whether TLS or authen‐
256 tication should be used.
257 An example of this file is:
259 <?xml version="1.0" ?>
261 <autofs_ldap_sasl_conf
262 usetls="yes"
263 tlsrequired="no"
264 authrequired="no"
265 authtype="DIGEST-MD5"
266 user="xyz"
267 secret="abc"
268 />
269 If TLS encryption is to be used the location of the Certificate Author‐
271 ity certificate must be set within the LDAP client configuration in or‐
272 der to validate the server certificate. If, in addition, a certified
273 connection is to be used then the client certificate and private key
274 file locations must also be configured within the LDAP client.
275 In OpenLDAP these may be configured in the ldap.conf file or in the
277 per-user configuration. For example it may be sensible to use the sys‐
278 tem wide configuration for the location of the Certificate Authority
279 certificate and set the location of the client certificate and private
280 key in the per-user configuration. The location of these files and the
281 configuration entry requirements is system dependent so the documenta‐
282 tion for your installation will need to be consulted to get further in‐
283 formation.
284 See autofs_ldap_auth.conf (5) for more information.
286
288 /- auto.data
289 /home /etc/auto.home
290 /mnt yp:mnt.map
291 This will generate two mountpoints for /home and /mnt and install di‐
293 rect mount triggers for each entry in the direct mount map auto.data.
294 All accesses to /home will lead to the consultation of the map in
295 /etc/auto.home and all accesses to /mnt will consult the NIS map
296 mnt.map. All accesses to paths in the map auto.data will trigger
297 mounts when they are accessed and the Name Service Switch configuration
298 will be used to locate the source of the map auto.data.
299
301 automount(8), autofs(5), autofs(8), autofs.conf(5), aut‐
302 ofs_ldap_auth.conf(5)
303
305 This manual page was written by Christoph Lameter <chris@waterf.org>,
306 for the Dean GNU/Linux system. Edited by <hpa@transmeta.com> and Ian
307 Kent <raven@themaw.net> .
308 11 Apr 2006 AUTO.MASTER(5)