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.
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: + [map‐
41 type,format:]map[options] and automount(8) will process the map accord‐
42 ing to the specification described below for map entries.
43
45 Master map entries have three fields separated by an arbitrary number
46 of spaces or tabs. Lines beginning with # are comments. The first field
47 is the mount point described above and the second field is the name of
48 the map to be consulted for the mount point followed by the third field
49 which contains options to be applied to all entries in the map.
50 The format of a master map entry is:
52 mount-point [map-type[,format]:]map [options]
54 mount-point
56 Base location for the autofs filesystem to be mounted. For in‐
57 direct maps this directory will be created (as with mkdir -p)
58 and is removed when the autofs filesystem is umounted.
59 map-type
61 Type of map used for this mount point. The following are valid
62 map types:
63 file The map is a regular text file.
65 program
67 The map is an executable program, which is passed a key
68 on the command line and returns an entry (everything be‐
69 sides the key) on stdout if successful.
70 yp The map is a NIS (YP) database.
72 nisplus
74 The map is a NIS+ database.
75 hesiod The map is a hesiod database whose filsys entries are
77 used for maps.
78 ldap or ldaps
80 The map is stored in an LDAP directory. If ldaps is used
81 the appropriate certificate must be configured in the
82 LDAP client.
83 format Format of the map data; currently the only formats recognized
85 are sun, which is a subset of the Sun automounter map format,
86 and hesiod, for hesiod filesys entries. If the format is left
87 unspecified, it defaults to sun for all map types except hesiod.
88 map Name of the map to use. This is an absolute UNIX pathname for
90 maps of types file or program, and the name of a database in the
91 case for maps of type yp, nisplus, or hesiod or the dn of an
92 LDAP entry for maps of type ldap.
93 options
95 Any remaining command line arguments without leading dashes (-)
96 are taken as options (-o) to mount. Arguments with leading
97 dashes are considered options for the maps.
98 The sun format supports the following options:
100 -Dvariable=value
102 Replace variable with value in map substitutions.
103 -strict
105 Treat errors when mounting file systems as fatal. This is
106 important when multiple file systems should be mounted
107 (`multimounts'). If this option is given, no file system
108 is mounted at all if at least one file system can't be
109 mounted.
110 nosymlink
112 This is an autofs specific option that is a pseudo mount
113 option and so is given without a leading dash. Histori‐
114 cally this option was used to prevent symlinking of local
115 NFS mounts. Nowadays it can be used to prevent bind
116 mounting of local NFS filesystems as well. If you need to
117 prevent bind mounting for only specific entrys in a map
118 then this can be done by adding the "port=" mount option
119 to the given entries.
120
122 The default value of several general settings may be changed in the
123 configuration file /etc/sysconfig/autofs. They are:
124 TIMEOUT
126 sets the default mount timeout (program default 600).
127 BROWSE_MODE
129 Maps are browsable by default (program default "yes").
130 APPEND_OPTIONS
132 Determine whether global options, given on the command line or
133 per mount in the master map, are appended to map entry options
134 or if the map entry options replace the global options (program
135 default "yes", append options).
136 LOGGING
138 set default log level "none", "verbose" or "debug" (program de‐
139 fault "none").
140
142 If "-hosts" is given as the map then accessing a key under the mount
143 point which corresponds to a hostname will allow access to the exports
144 of that host.
145 For example, with an entry in the master map of /net -hosts accessing
147 /net/myserver will mount exports from myserver on directories below
148 /net/myserver.
149 NOTE: mounts done from a hosts map will be mounted with the "nosuid"
151 and "nodev" options unless the options "suid" and "dev" are explicitly
152 given in the master map entry.
153
155 If the map type ldap is specified the mapname is of the form [//server‐
156 name/]dn, where the optional servername is the name of the LDAP server
157 to query, and dn is the Distinguished Name of a subtree to search for
158 map entries. The old style ldap:servername:mapname is also understood.
159 Alternatively, the type can be obtained from the Name Service Switch
160 configuration, in which case the map name alone must be given.
161 If no schema is set in the autofs configuration then autofs will check
163 each of the commonly used schema for a valid entry and if one is found
164 it will used for subsequent lookups.
165 There are three common schemas in use:
167 nisMap Entries in the nisMap schema are nisObject objects in the speci‐
169 fied subtree, where the cn attribute is the key (the wildcard
170 key is "/"), and the nisMapEntry attribute contains the informa‐
171 tion used by the automounter.
172 automountMap
174 The automountMap schema has two variations that differ in the
175 attribute used for the map key. Entries in the automountMap
176 schema are automount objects in the specified subtree, where the
177 cn or automountKey attribute (depending on local usage) is the
178 key (the wildcard key is "/"), and the automountInformation at‐
179 tribute contains the information used by the automounter. Note
180 that the cn attribute is case insensitive.
181 The object classes and attributes used for accessing automount maps in
183 LDAP can be changed by setting entries in the autofs configuration lo‐
184 cated in /etc/sysconfig/autofs.
185 NOTE: If a schema is given in the configuration then all the schema
187 configuration values must be set, any partial schema specifica‐
188 tion will be ignored.
189 The configuration settings available are:
191 MAP_OBJECT_CLASS
193 The map object class. In the nisMap schema this corresponds to
194 the class nisMap and in the automountMap schema it corresponds
195 to the class automountMap.
196 ENTRY_OBJECT_CLASS
198 The map entry object class. In the nisMap schema this corre‐
199 sponds to the class nisObject and in the automountMap schema it
200 corresponds to the class automount.
201 MAP_ATTRIBUTE
203 The attribute used to identify the name of the map to which this
204 entry belongs. In the nisMap schema this corresponds to the at‐
205 tribute nisMapName and in the automountMap schema it corresponds
206 to the attribute ou or automountMapName.
207 ENTRY_ATTRIBUTE
209 The attribute used to identify a map key. In the nisMap schema
210 this corresponds to the attribute cn and in the automountMap
211 schema it corresponds to the attribute automountKey.
212 VALUE_ATTRIBUTE
214 The attribute used to identify the value of the map entry. In
215 the nisMap schema this corresponds to the attribute nisMapEntry
216 and in the automountMap schema it corresponds to the attribute
217 automountInformation.
218 NOTE: It is essential that entries use class and attribute in a con‐
220 sistent manner for correct operation of autofs. For example mix‐
221 ing cn and automountKey attributes in automount schema map en‐
222 tries won't work as expected.
223
225 LDAP authenticated binds, TLS encrypted connections and certification
226 may be used by setting appropriate values in the autofs authentication
227 configuration file and configuring the LDAP client with appropriate
228 settings. The default location of this file is
229 /etc/autofs_ldap_auth.conf. If this file exists it will be used to es‐
230 tablish whether TLS or authentication should be used.
231 An example of this file is:
233 <?xml version="1.0" ?>
235 <autofs_ldap_sasl_conf
236 usetls="yes"
237 tlsrequired="no"
238 authrequired="no"
239 authtype="DIGEST-MD5"
240 user="xyz"
241 secret="abc"
242 />
243 If TLS encryption is to be used the location of the Certificate Author‐
245 ity certificate must be set within the LDAP client configuration in or‐
246 der to validate the server certificate. If, in addition, a certified
247 connection is to be used then the client certificate and private key
248 file locations must also be configured within the LDAP client.
249 In OpenLDAP these may be configured in the ldap.conf file or in the
251 per-user configuration. For example it may be sensible to use the sys‐
252 tem wide configuration for the location of the Certificate Authority
253 certificate and set the location of the client certificate and private
254 key in the per-user configuration. The location of these files and the
255 configuration entry requirements is system dependent so the documenta‐
256 tion for your installation will need to be consulted to get further in‐
257 formation.
258
260 /- auto.data
261 /home /etc/auto.home
262 /mnt yp:mnt.map
263 This will generate two mountpoints for /home and /mnt and install di‐
265 rect mount triggers for each entry in the direct mount map auto.data.
266 All accesses to /home will lead to the consultation of the map in
267 /etc/auto.home and all accesses to /mnt will consult the NIS map
268 mnt.map. All accesses to paths in the map auto.data will trigger
269 mounts when they are accessed and the Name Service Switch configuration
270 will be used to locate the source of the map auto.data.
271
273 automount(8), autofs(5), autofs(8).
274
276 This manual page was written by Christoph Lameter <chris@waterf.org>,
277 for the Dean GNU/Linux system. Edited by <hpa@transmeta.com> and Ian
278 Kent <raven@themaw.net> .
279 11 Apr 2006 AUTO.MASTER(5)