2 .\" Copyright (c) 1997-2014 Erez Zadok
3 .\" Copyright (c) 1989 Jan-Simon Pendry
4 .\" Copyright (c) 1989 Imperial College of Science, Technology & Medicine
5 .\" Copyright (c) 1989 The Regents of the University of California.
6 .\" All rights reserved.
8 .\" This code is derived from software contributed to Berkeley by
9 .\" Jan-Simon Pendry at Imperial College, London.
11 .\" Redistribution and use in source and binary forms, with or without
12 .\" modification, are permitted provided that the following conditions
14 .\" 1. Redistributions of source code must retain the above copyright
15 .\" notice, this list of conditions and the following disclaimer.
16 .\" 2. Redistributions in binary form must reproduce the above copyright
17 .\" notice, this list of conditions and the following disclaimer in the
18 .\" documentation and/or other materials provided with the distribution.
19 .\" 3. Neither the name of the University nor the names of its contributors
20 .\" may be used to endorse or promote products derived from this software
21 .\" without specific prior written permission.
23 .\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
24 .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
25 .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
26 .\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
27 .\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
28 .\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
29 .\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
30 .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
31 .\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
32 .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
36 .\" File: am-utils/amd/amd.8
44 .Nd automatically mount file systems
52 .Op Fl a Ar mount_point
55 .Op Fl k Ar kernel-arch
57 .Op Fl o Ar op_sys_ver
58 .Op Fl t Ar timeout.retransmit
60 .Op Fl x Ar log-option
63 .Op Fl C Ar cluster-name
66 .Op Fl O Ar op_sys_name
77 is a daemon that automatically mounts file systems
78 whenever a file or directory
79 within that file system is accessed.
80 File systems are automatically unmounted when they
81 appear to be quiescent.
86 operates by attaching itself as an
88 server to each of the specified
90 Lookups within the specified directories
93 which uses the map defined by
95 to determine how to resolve the lookup.
96 Generally, this will be a host name, some file system information
97 and some mount options for the given file system.
99 In the first form depicted above,
101 will print a short help string.
102 In the second form, if no options are
107 will read configuration parameters from the file
111 The last form is described below.
113 .Bl -tag -width indent
114 .It Fl a Ar temporary-directory
115 Specify an alternative location for the real mount points.
121 in seconds, that a looked up name remains
122 cached when not in use.
123 The default is 5 minutes.
125 Specify the local domain name.
126 If this option is not
127 given the domain name is determined from the hostname.
128 .It Fl k Ar kernel-arch
129 Specifies the kernel architecture.
131 to set the ${karch} selector.
133 Specify a logfile in which to record mount and unmount events.
138 then the log messages will be sent to the system log daemon by
140 The default syslog facility used is
143 wish to change it, append its name to the log file name, delimited by a
151 will log messages via
155 facility (if it exists on the system).
158 The name referred to by ${rhost} is normalized relative to the
159 host database before being used.
160 The effect is to translate
164 .It Fl o Ar op_sys_ver
165 Override the compiled-in version number of the operating system.
167 when the built in version is not desired for backward compatibility reasons.
168 For example, if the build in version is
170 you can override it to
172 and use older maps that were written with the latter in mind.
175 Outputs the process ID of
177 to standard output where it can be saved into a file.
179 Restart existing mounts.
183 will scan the mount file table to determine which file systems
184 are currently mounted.
185 Whenever one of these would have
190 .It Fl t Ar timeout.retransmit
194 in tenths of a second, between
196 retries (for UDP only).
199 The second value alters the retransmit counter, which
200 defaults to 11 retransmissions.
201 Both of these values are used by the kernel
202 to communicate with amd.
203 Useful defaults are supplied if either or both
209 relies on the kernel RPC retransmit mechanism to trigger mount retries.
210 The values of these parameters change the overall retry interval.
212 an interval gives poor interactive response; too short an interval causes
216 Displays version and configuration information on standard error.
220 in seconds, between attempts to dismount
221 file systems that have exceeded their cached times.
222 The default is 2 minutes.
225 Specify run-time logging options. The options are a comma separated
227 .Li fatal, error, user, warn, info, map, stats, defaults, all .
228 Note that "fatal" and "error" are mandatory and cannot be turned off.
231 Specify an alternative
233 domain from which to fetch the
236 The default is the system domain name. This option is ignored if NIS
237 support is not available.
239 Specifies the OS architecture.
240 This is used solely to set the ${arch}
242 .It Fl C Ar cluster-name
243 Specify an alternative HP-UX cluster name to use.
245 Select from a variety of debug options.
247 option with the string
249 reverses the effect of that option.
250 Options are cumulative.
251 The most useful option is
256 is only used for debugging other options are not documented here:
257 the current supported set of options is listed by the
260 and a fuller description is available in the program source.
261 .It Fl F Ar conf_file
264 configuration file to use.
267 for description of this file's format.
268 This configuration file is used to
269 specify any options in lieu of typing many of them on the command line.
272 file includes directives for every command line option amd has, and many
273 more that are only available via the configuration file facility.
275 configuration file specified by this option is processed after all other
276 options had been processed, regardless of the actual location of this option
279 Print help and usage string.
280 .It Fl O Ar op_sys_name
281 Override the compiled-in name of the operating system.
283 built in name is not desired for backward compatibility reasons.
285 example, if the build in name is
287 you can override it to
289 and use older maps which were written with the latter in mind.
291 Do not lock the running executable pages of
296 performance, systems that support the
301 This way there is less chance
302 the operating system will schedule, page out, and swap the
306 This tends to improve
308 performance, at the cost of reserving the
311 process (making it unavailable for other processes).
312 If this behavior is not desired, use the
316 Specify a tag to use with
318 All map entries tagged with
321 Map entries that are not tagged are always processed.
322 Map entries that are tagged with a tag other than
324 will not be processed.
327 .Bl -tag -width ".Pa /etc/amd.conf"
329 directory under which file systems are dynamically mounted
331 default configuration file
334 Some care may be required when creating a mount map.
338 file system can be incredibly inefficient.
339 In most implementations of
341 their interpolations are not cached
342 by the kernel and each time a symbolic link is encountered during a
344 translation it costs an
349 It would appear that a large improvement in real-time
350 performance could be gained by adding a cache somewhere.
351 Replacing symlinks with a suitable incarnation of the auto-mounter
352 results in a large real-time speedup, but also causes a large
353 number of process context switches.
355 A weird imagination is most useful to gain full advantage of all
373 .%B "Linux NFS and Automounter Administration"
374 .%O ISBN 0-7821-2739-8
379 .Pa http://www.am-utils.org/
381 .%T Amd \- The 4.4 BSD Automounter
386 utility first appeared in
389 .An Jan-Simon Pendry Aq jsp@doc.ic.ac.uk ,
390 Department of Computing, Imperial College, London, UK.
392 .An Erez Zadok Aq ezk@cs.sunysb.edu ,
393 Computer Science Department, Stony Brook
394 University, Stony Brook, New York, USA.
396 Other authors and contributors to am-utils are listed in the
398 file distributed with am-utils.