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