1 '\" te
2 .\" Copyright 1989 AT&T
3 .\" Copyright (c) 2008, Sun Microsystems, Inc. All Rights Reserved
4 .\" Copyright 2015 Nexenta Systems, Inc. All rights reserved.
5 .\" The contents of this file are subject to the terms of the Common Development and Distribution License (the "License"). You may not use this file except in compliance with the License.
6 .\" You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE or http://www.opensolaris.org/os/licensing. See the License for the specific language governing permissions and limitations under the License.
7 .\" When distributing Covered Code, include this CDDL HEADER in each file and include the License file at usr/src/OPENSOLARIS.LICENSE. If applicable, add the following below this CDDL HEADER, with the fields enclosed by brackets "[]" replaced with your own identifying information: Portions Copyright [yyyy] [name of copyright owner]
8 .TH AUTOMOUNT 1M "Sep 8, 2015"
9 .SH NAME
10 automount \- install automatic mount points
11 .SH SYNOPSIS
12 .LP
13 .nf
14 \fB/usr/sbin/automount\fR [\fB-t\fR \fIduration\fR] [\fB-v\fR]
15 .fi
16
17 .SH DESCRIPTION
18 .sp
19 .LP
20 The \fBautomount\fR utility installs \fBautofs\fR mount points and associates
21 an automount map with each mount point. It starts the \fBautomountd\fR(1M)
22 daemon if it finds any non-trivial entries in either local or distributed
23 automount maps and if the daemon is not already running. The \fBautofs\fR file
24 system monitors attempts to access directories within it and notifies the
25 \fBautomountd\fR(1M) daemon. The daemon uses the map to locate a file system,
26 which it then mounts at the point of reference within the \fBautofs\fR file
27 system. A map can be assigned to an \fBautofs\fR mount using an entry in the
28 \fB/etc/auto_master\fR map or a direct map.
29 .sp
30 .LP
31 If the file system is not accessed within an appropriate interval (\fB10\fR
32 minutes by default), the \fBautomountd\fR daemon unmounts the file system.
33 .sp
34 .LP
35 The file \fB/etc/auto_master\fR determines the locations of all \fBautofs\fR
36 mount points. By default, this file contains three entries:
37 .sp
38 .in +2
39 .nf
40 # Master map for automounter
41 #
42 +auto_master
43 /net -hosts -nosuid
44 /home auto_home
45 .fi
46 .in -2
47 .sp
48
49 .sp
50 .LP
51 The \fB+auto_master\fR entry is a reference to an external \fBNIS\fR or
52 \fBNIS+\fR master map. If one exists, then its entries are read as if they
53 occurred in place of the \fB+auto_master\fR entry. The remaining entries in the
54 master file specify a directory on which an \fBautofs\fR mount will be made
55 followed by the automounter map to be associated with it. Optional mount
56 options may be supplied as an optional third field in the each entry. These
57 options are used for any entries in the map that do not specify mount options
58 explicitly. The \fBautomount\fR command is usually run without arguments. It
59 compares the entries \fB/etc/auto_master\fR with the current list of
60 \fBautofs\fR mounts in \fB/etc/mnttab\fR and adds, removes or updates
61 \fBautofs\fR mounts to bring the \fB/etc/mnttab\fR up to date with the
62 \fB/etc/auto_master\fR. At boot time it installs all \fBautofs\fR mounts from
63 the master map. Subsequently, it may be run to install \fBautofs\fR mounts for
64 new entries in the master map or the direct map, or to perform unmounts for
65 entries that have been removed from these maps.
66 .SS "Automount with Solaris Trusted Extensions"
67 .sp
68 .LP
69 If a system is configured with Solaris Trusted Extensions, additional
70 processing is performed to facilitate multilevel home directory access. A list
71 of zones whose labels are dominated by the current zone is generated and
72 default \fBauto_home\fR automount maps are generated if they do not currently
73 exist. These automount maps are named \fBauto_home_\fR\fI<zonename>\fR, where
74 \fI<zonename>\fR is the name of each zone's lower-level zone. An \fBautofs\fR
75 mount of each such \fBauto_home\fR map is then performed, regardless of whether
76 it is explicitly or implicitly listed in the master map. Instead of
77 \fBautofs\fR mounting the standard \fBauto_home\fR map, the zone uses an
78 \fBauto_home\fR file appended with its own zone name. Each zone's
79 \fBauto_home\fR map is uniquely named so that it can be maintained and shared
80 by all zones using a common name server.
81 .sp
82 .LP
83 By default, the home directories of lower-level zones are mounted read-only
84 under \fB/zone/\fI<zonename>\fR/export/home\fR when each zone is booted. The
85 default \fBauto_home_\fR\fI<zonename>\fR automount map specifies that path as
86 the source directory for an \fBlofs\fR remount onto
87 \fB/zone/\fI<zonename>\fR/home/\fI<username>\fR\fR. For example, the file
88 \fBauto_home_public\fR, as generated from a higher level zone would contain:
89 .sp
90 .LP
91 +auto_home_public
92 .sp
93 .LP
94 * -fstype=lofs :/zone/public/export/home/&
95 .sp
96 .LP
97 When a home directory is referenced and the name does not match any other keys
98 in the \fBauto_home_public\fR map, it will match this loopback mount
99 specification. If this loopback match occurs and the name corresponds to a
100 valid user whose home directory does not exist in the public zone, the
101 directory is automatically created on behalf of the user.
102 .SH OPTIONS
103 .sp
104 .LP
105 The following options are supported:
106 .sp
107 .ne 2
108 .na
109 \fB\fB-t\fR \fIduration\fR\fR
110 .ad
111 .RS 15n
112 Specifies a \fIduration\fR, in seconds, that a file system is to remain mounted
113 when not in use. The default is \fB10\fR minutes.
114 .RE
115
116 .sp
117 .ne 2
118 .na
119 \fB\fB-v\fR\fR
120 .ad
121 .RS 15n
122 Verbose mode. Notifies of \fBautofs\fR mounts, unmounts, or other non-essential
123 information.
124 .RE
125
126 .SH USAGE
127 .SS "Map Entry Format"
128 .sp
129 .LP
130 A simple map entry (mapping) takes the form:
131 .sp
132 .in +2
133 .nf
134 key [ -\fImount-options\fR ] \fIlocation\fR .\|.\|.
135 .fi
136 .in -2
137 .sp
138
139 .sp
140 .LP
141 where \fBkey\fR is the full pathname of the directory to mount when used in a
142 direct map, or the simple name of a subdirectory in an indirect map.
143 \fImount-options\fR is a comma-separated list of \fBmount\fR options, and
144 \fIlocation\fR specifies a file system from which the directory may be mounted.
145 In the case of a simple \fBNFS\fR mount, the options that can be used are
146 specified in \fBmount_nfs\fR(1M), and \fIlocation\fR takes the form:
147 .sp
148 .in +2
149 .nf
150 \fIhost\fR\fB:\|\fR\fIpathname\fR
151 .fi
152 .in -2
153 .sp
154
155 .sp
156 .LP
157 \fIhost\fR is the name of the host from which to mount the file system, and
158 \fIpathname\fR is the absolute pathname of the directory to mount.
159 .sp
160 .LP
161 Options to other file systems are documented in the other \fBmount_*\fR
162 reference manual pages.
163 .SS "Replicated File Systems"
164 .sp
165 .LP
166 Multiple \fIlocation\fR fields can be specified for replicated \fBNFS\fR file
167 systems, in which case \fBautomount\fR and the kernel will each try to use that
168 information to increase availability. If the read-only flag is set in the map
169 entry, \fBautomountd\fR mounts a list of locations that the kernel may use,
170 sorted by several criteria. Only locations available at mount time will be
171 mounted, and thus be available to the kernel. When a server does not respond,
172 the kernel will switch to an alternate server. The sort ordering of
173 \fBautomount\fR is used to determine how the next server is chosen. If the
174 read-only flag is not set, \fBautomount\fR will mount the best single location,
175 chosen by the same sort ordering, and new servers will only be chosen when an
176 unmount has been possible, and a remount is done. Servers on the same local
177 subnet are given the strongest preference, and servers on the local net are
178 given the second strongest preference. Among servers equally far away, response
179 times will determine the order if no weighting factors (see below) are used.
180 .sp
181 .LP
182 If the list includes server locations using both the \fBNFS\fR Version 2
183 Protocol and the \fBNFS\fR Version 3 Protocol, \fBautomount\fR will choose only
184 a subset of the server locations on the list, so that all entries will be the
185 same protocol. It will choose servers with the \fBNFS\fR Version 3 Protocol so
186 long as an \fBNFS\fR Version 2 Protocol server on a local subnet will not be
187 ignored. See the \fI\fR for additional details.
188 .sp
189 .LP
190 If each \fIlocation\fR in the list shares the same \fIpathname\fR then a single
191 \fIlocation\fR may be used with a comma-separated list of hostnames:
192 .sp
193 .in +2
194 .nf
195 \fBhostname\fR\fB,\fR\fBhostname\fR\|.\|.\|.\|\fB:\fR\|\fIpathname\fR
196 .fi
197 .in -2
198 .sp
199
200 .sp
201 .LP
202 Requests for a server may be weighted, with the weighting factor appended to
203 the server name as an integer in parentheses. Servers without a weighting are
204 assumed to have a value of zero (most likely to be selected). Progressively
205 higher values decrease the chance of being selected. In the example,
206 .sp
207 .in +2
208 .nf
209 \fBman\fR -ro \fBalpha,bravo,charlie(1),delta(4)\|:\|/usr/man\fR
210 .fi
211 .in -2
212 .sp
213
214 .sp
215 .LP
216 hosts \fBalpha\fR and \fBbravo\fR have the highest priority; host \fBdelta\fR
217 has the lowest.
218 .sp
219 .LP
220 Server proximity takes priority in the selection process. In the example above,
221 if the server \fBdelta\fR is on the same network segment as the client, but the
222 others are on different network segments, then \fBdelta\fR will be selected;
223 the weighting value is ignored. The weighting has effect only when selecting
224 between servers with the same network proximity. The automounter always selects
225 the localhost over other servers on the same network segment, regardless of
226 weighting.
227 .sp
228 .LP
229 In cases where each server has a different export point, the weighting can
230 still be applied. For example:
231 .sp
232 .in +2
233 .nf
234 man -ro alpha:/usr/man bravo,charlie(1):/usr/share/man
235 delta(3):/export/man
236 .fi
237 .in -2
238 .sp
239
240 .sp
241 .LP
242 A mapping can be continued across input lines by escaping the \fBNEWLINE\fR
243 with a backslash (\e) Comments begin with a number sign (\fB#\fR) and end at
244 the subsequent NEWLINE.
245 .SS "Map Key Substitution"
246 .sp
247 .LP
248 The ampersand (\fB&\fR) character is expanded to the value of the \fBkey\fR
249 field for the entry in which it occurs. In this case:
250 .sp
251 .in +2
252 .nf
253 \fBjane\fR \fBsparcserver\|:\|/home/&\fR
254 .fi
255 .in -2
256 .sp
257
258 .sp
259 .LP
260 the \fB&\fR expands to \fBjane\fR.
261 .SS "Wildcard Key"
262 .sp
263 .LP
264 The asterisk (\fB*\fR) character, when supplied as the \fBkey\fR field, is
265 recognized as the catch-all entry. Such an entry will match any key not
266 previously matched. For instance, if the following entry appeared in the
267 indirect map for \fB/config\fR:
268 .sp
269 .in +2
270 .nf
271 * &\|:\|/export/config/&
272 .fi
273 .in -2
274 .sp
275
276 .sp
277 .LP
278 this would allow automatic mounts in \fB/config\fR of any remote file system
279 whose location could be specified as:
280 .sp
281 .in +2
282 .nf
283 hostname\|:\|/export/config/hostname
284 .fi
285 .in -2
286 .sp
287
288 .sp
289 .LP
290 Note that the wildcard key does not work in conjunction with the \fB-browse\fR
291 option.
292 .SS "Variable Substitution"
293 .sp
294 .LP
295 Client specific variables can be used within an \fBautomount\fR map. For
296 instance, if \fB$HOST\fR appeared within a map, \fBautomount\fR would expand it
297 to its current value for the client's host name. Supported variables are:
298 .sp
299
300 .sp
301 .TS
302 l l l
303 l l l .
304 \fBARCH\fR The output of \fBarch\fR T{
305 The architecture name. For example, \fBsun4\fR on a sun4u machine.
306 T}
307 \fBCPU\fR The output of \fBuname\fR \fB-p\fR The processor type.
308 For example, "sparc"
309 \fBHOST\fR The output of \fBuname\fR \fB-n\fR The host name.
310 For example, \fBmyhost\fR.
311 \fBKARCH\fR The output of \fBarch -k\fR or \fBuname -m\fR T{
312 The kernel architecture name or machine hardware name. For example, \fBsun4u\fR.
313 T}
314
315 \fBOSNAME\fR The output of \fBuname\fR \fB-s\fR The OS name.
316 For example, "SunOS"
317 \fBOSREL\fR The output of \fBuname\fR \fB-r\fR The OS release name.
318 For example "5.3"
319 \fBOSVERS\fR The output of \fBuname\fR \fB-v\fR The OS version.
320 For example, "beta1.0"
321 \fBNATISA\fR The output of \fBisainfo\fR \fB-n\fR T{
322 The native instruction set architecture for the system.
323 T}
324 For example, "sparcv9"
325 \fBPLATFORM\fR The output of \fBuname -i\fR T{
326 The platform name. For example, \fBSUNW,Sun-Fire-V240\fR.
327 T}
328
329 .TE
330
331 .sp
332 .LP
333 If a reference needs to be protected from affixed characters, you can surround
334 the variable name with curly braces (\fB\|{\|}\|\fR).
335 .SS "Multiple Mounts"
336 .sp
337 .LP
338 A multiple mount entry takes the form:
339 .sp
340 .in +2
341 .nf
342 key [\fI-mount-options\fR] [\|[\fImountpoint\fR] [\fI-mount-options\fR] \fIlocation\fR.\|.\|.\|]\|.\|.\|.
343 .fi
344 .in -2
345 .sp
346
347 .sp
348 .LP
349 The initial \fB/\fR[\fImountpoint\fR\|] is optional for the first mount and
350 mandatory for all subsequent mounts. The optional \fImountpoint\fR is taken as
351 a pathname relative to the directory named by \fBkey\fR. If \fImountpoint\fR is
352 omitted in the first occurrence, a \fImountpoint\fR of \fB/\fR (root) is
353 implied.
354 .sp
355 .LP
356 Given an entry in the indirect map for \fB/src\fR
357 .sp
358 .in +2
359 .nf
360 beta -ro\e
361 / svr1,svr2:/export/src/beta \e
362 /1.0 svr1,svr2:/export/src/beta/1.0 \e
363 /1.0/man svr1,svr2:/export/src/beta/1.0/man
364 .fi
365 .in -2
366 .sp
367
368 .sp
369 .LP
370 All offsets must exist on the server under \fBbeta\fR. \fBautomount\fR will
371 automatically mount \fB/src/beta\fR, \fB/src/beta/1.0\fR, and
372 \fB/src/beta/1.0/man\fR, as needed, from either \fBsvr1\fR or \fBsvr2\fR,
373 whichever host is nearest and responds first.
374 .SS "Other File System Types"
375 .sp
376 .LP
377 The automounter assumes \fBNFS\fR mounts as a default file system type. Other
378 file system types can be described using the \fBfstype\fR mount option. Other
379 mount options specific to this file system type can be combined with the
380 \fBfstype\fR option. The location field must contain information specific to
381 the file system type. If the location field begins with a slash, a colon
382 character must be prepended, for instance, to mount a CD file system:
383 .sp
384 .in +2
385 .nf
386 \fBcdrom -fstype=hsfs,ro :\|/dev/sr0\fR
387 .fi
388 .in -2
389 .sp
390
391 .sp
392 .LP
393 or to perform an \fBautofs\fR mount:
394 .sp
395 .in +2
396 .nf
397 \fBsrc\fR \fB-fstype\fR\fB=autofs auto_src\fR
398 .fi
399 .in -2
400 .sp
401
402 .sp
403 .LP
404 Use this procedure only if you are not using Volume Manager.
405 .sp
406 .LP
407 See the \fBNOTES\fR section for information on option inheritance.
408 .SS "Indirect Maps"
409 .sp
410 .LP
411 An indirect map allows you to specify mappings for the subdirectories you wish
412 to mount under the \fBdirectory\fR indicated on the command line. In an
413 indirect map, each \fBkey\fR consists of a simple name that refers to one or
414 more file systems that are to be mounted as needed.
415 .SS "Direct Maps"
416 .sp
417 .LP
418 Entries in a direct map are associated directly with \fBautofs\fR mount points.
419 Each \fIkey\fR is the full pathname of an \fBautofs\fR mount point. The direct
420 map as a whole is not associated with any single directory.
421 .sp
422 .LP
423 Direct maps are distinguished from indirect maps by the \fB/-\fR key. For
424 example:
425 .sp
426 .in +2
427 .nf
428 # Master map for automounter
429 #
430 +auto_master
431 /net -hosts -nosuid,nobrowse
432 /home auto_home -nobrowse
433 /- auto_direct
434 .fi
435 .in -2
436 .sp
437
438 .SS "Included Maps"
439 .sp
440 .LP
441 The contents of another map can be included within a map with an entry of the
442 form
443 .sp
444 .in +2
445 .nf
446 +\fImapname\fR
447 .fi
448 .in -2
449 .sp
450
451 .sp
452 .LP
453 If \fImapname\fR begins with a slash, it is assumed to be the pathname of a
454 local file. Otherwise, the location of the map is determined by the policy of
455 the name service switch according to the entry for the automounter in
456 \fB/etc/nsswitch.conf\fR, such as
457 .sp
458 .in +2
459 .nf
460 automount: files nis
461 .fi
462 .in -2
463 .sp
464
465 .sp
466 .LP
467 If the name service is \fBfiles\fR, then the name is assumed to be that of a
468 local file in \fB/etc\fR. If the key being searched for is not found in the
469 included map, the search continues with the next entry.
470 .SS "Special Maps"
471 .sp
472 .LP
473 There are two special maps available: \fB-hosts\fR and \fB-null\fR. The
474 \fB-hosts\fR map is used with the \fB/net\fR directory and assumes that the map
475 key is the hostname of an \fBNFS\fR server. The \fBautomountd\fR daemon
476 dynamically constructs a map entry from the server's list of exported file
477 systems. References to a directory under \fB/net/hermes\fR will refer to the
478 corresponding directory relative to \fBhermes\fR root.
479 .sp
480 .LP
481 The \fB-null\fR map cancels a previous map for the directory indicated. This is
482 most useful in the \fB/etc/auto_master\fR for cancelling entries that would
483 otherwise be inherited from the \fB+auto_master\fR include entry. To be
484 effective, the \fB-null\fR entries must be inserted before the included map
485 entry.
486 .SS "Executable Maps"
487 .sp
488 .LP
489 Local maps that have the execute bit set in their file permissions will be
490 executed by the automounter and provided with a key to be looked up as an
491 argument. The executable map is expected to return the content of an
492 automounter map entry on its stdout or no output if the entry cannot be
493 determined. A direct map cannot be made executable.
494 .SS "Configuration and the auto_master Map"
495 .sp
496 .LP
497 When initiated without arguments, \fBautomount\fR consults the master map for a
498 list of \fBautofs\fR mount points and their maps. It mounts any \fBautofs\fR
499 mounts that are not already mounted, and unmounts \fBautofs\fR mounts that have
500 been removed from the master map or direct map.
501 .sp
502 .LP
503 The master map is assumed to be called \fBauto_master\fR and its location is
504 determined by the name service switch policy. Normally the master map is
505 located initially as a local file \fB/etc/auto_master\fR.
506 .SS "Browsing"
507 .sp
508 .LP
509 The \fBautomount\fR daemon supports browsability of indirect maps. This allows
510 all of the potential mount points to be visible, whether or not they are
511 mounted. The \fB-nobrowse\fR option can be added to any indirect \fBautofs\fR
512 map to disable browsing. For example:
513 .sp
514 .in +2
515 .nf
516 /net -hosts -nosuid,nobrowse
517 /home auto_home
518 .fi
519 .in -2
520 .sp
521
522 .sp
523 .LP
524 In this case, any \fIhostnames\fR would only be visible in \fB/net\fR after
525 they are mounted, but all potential mount points would be visible under
526 \fB/home\fR. The \fB-browse\fR option enables browsability of \fBautofs\fR file
527 systems. This is the default for all indirect maps.
528 .sp
529 .LP
530 The \fB-browse\fR option does not work in conjunction with the wildcard key.
531 .SS "Restricting Mount Maps"
532 .sp
533 .LP
534 Options specified for a map are used as the default options for all the entries
535 in that map. They are ignored when map entries specify their own mount options.
536 .sp
537 .LP
538 In some cases, however, it is desirable to force \fBnosuid\fR, \fBnodevices\fR,
539 \fBnosetuid\fR, or \fBnoexec\fR for a complete mount map and its submounts.
540 This can be done by specifying the additional mount option, \fB-restrict\fR.
541 .sp
542 .in +2
543 .nf
544 /home auto_home -restrict,nosuid,hard
545 .fi
546 .in -2
547 .sp
548
549 .sp
550 .LP
551 The \fB-restrict\fR option forces the inheritance of all the restrictive
552 options \fBnosuid\fR, \fBnodevices\fR, \fBnosetuid\fR, and \fBnoexec\fR as well
553 as the restrict option itself. In this particular example, the \fBnosuid\fR and
554 \fBrestrict\fR option are inherited but the \fBhard\fR option is not. The
555 \fBrestrict\fR option also prevents the execution of "executable maps" and is
556 enforced for auto mounts established by programs with fewer than all privileges
557 available in their zone.
558 .SH EXIT STATUS
559 .sp
560 .LP
561 The following exit values are returned:
562 .sp
563 .ne 2
564 .na
565 \fB\fB0\fR\fR
566 .ad
567 .RS 5n
568 Successful completion.
569 .RE
570
571 .sp
572 .ne 2
573 .na
574 \fB\fB1\fR\fR
575 .ad
576 .RS 5n
577 An error occurred.
578 .RE
579
580 .SH FILES
581 .sp
582 .ne 2
583 .na
584 \fB\fB/etc/auto_master\fR\fR
585 .ad
586 .RS 23n
587 Master automount map.
588 .RE
589
590 .sp
591 .ne 2
592 .na
593 \fB\fB/etc/auto_home\fR\fR
594 .ad
595 .RS 23n
596 Map to support automounted home directories.
597 .RE
598
599 .sp
600 .ne 2
601 .na
602 \fB\fB/etc/default/autofs\fR\fR
603 .ad
604 .RS 23n
605 Supplies default values for parameters for \fBautomount\fR and
606 \fBautomountd\fR. See \fBautofs\fR(4).
607 .RE
608
609 .sp
610 .ne 2
611 .na
612 \fB\fB/etc/nsswitch.conf\fR\fR
613 .ad
614 .RS 23n
615 Name service switch configuration file. See \fBnsswitch.conf\fR(4).
616 .RE
617
618 .SH SEE ALSO
619 .sp
620 .LP
621 \fBisainfo\fR(1), \fBls\fR(1), \fBsvcs\fR(1), \fBuname\fR(1),
622 \fBautomountd\fR(1M), \fBmount\fR(1M), \fBmount_nfs\fR(1M),
623 \fBsvcadm\fR(1M), \fBautofs\fR(4), \fBattributes\fR(5),
624 \fBnfssec\fR(5), \fBsmf\fR(5)
625 .sp
626 .LP
627 \fI\fR
628 .SH NOTES
629 .sp
630 .LP
631 \fBautofs\fR mount points must not be hierarchically related. \fBautomount\fR
632 does not allow an \fBautofs\fR mount point to be created within another
633 \fBautofs\fR mount.
634 .sp
635 .LP
636 Since each direct map entry results in a new \fBautofs\fR mount such maps
637 should be kept short.
638 .sp
639 .LP
640 Entries in both direct and indirect maps can be modified at any time. The new
641 information is used when \fBautomountd\fR next uses the map entry to do a
642 mount.
643 .sp
644 .LP
645 New entries added to a master map or direct map will not be useful until the
646 automount command is run to install them as new \fBautofs\fR mount points. New
647 entries added to an indirect map may be used immediately.
648 .sp
649 .LP
650 As of the Solaris 2.6 release, a listing (see \fBls\fR(1)) of the \fBautofs\fR
651 directory associated with an indirect map shows all potential mountable
652 entries. The attributes associated with the potential mountable entries are
653 temporary. The real file system attributes will only be shown once the file
654 system has been mounted.
655 .sp
656 .LP
657 Default mount options can be assigned to an entire map when specified as an
658 optional third field in the master map. These options apply only to map entries
659 that have no mount options. Note that map entities with options override the
660 default options, as at this time, the options do not concatenate. The
661 concatenation feature is planned for a future release.
662 .sp
663 .LP
664 When operating on a map that invokes an NFS mount, the default number of
665 retries for the automounter is 0, that is, a single mount attempt, with no
666 retries. Note that this is significantly different from the default (10000) for
667 the \fBmount_nfs\fR(1M) utility.
668 .sp
669 .LP
670 The Network Information Service (NIS) was formerly known as Sun Yellow Pages
671 (YP). The functionality of the two remains the same.
672 .sp
673 .LP
674 The \fBautomount\fR service is managed by the service management facility,
675 \fBsmf\fR(5), under the service identifier:
676 .sp
677 .in +2
678 .nf
679 svc:/system/filesystem/autofs:default
680 .fi
681 .in -2
682 .sp
683
684 .sp
685 .LP
686 Administrative actions on this service, such as enabling, disabling, or
687 requesting restart, can be performed using \fBsvcadm\fR(1M). The service's
688 status can be queried using the \fBsvcs\fR(1) command.