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