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
79 base system is deprecated and will be removed before
81 Users are advised to use
85 port or package instead.
91 is a daemon that automatically mounts file systems
92 whenever a file or directory
93 within that file system is accessed.
94 File systems are automatically unmounted when they
95 appear to be quiescent.
100 operates by attaching itself as an
102 server to each of the specified
104 Lookups within the specified directories
107 which uses the map defined by
109 to determine how to resolve the lookup.
110 Generally, this will be a host name, some file system information
111 and some mount options for the given file system.
113 In the first form depicted above,
115 will print a short help string.
116 In the second form, if no options are
121 will read configuration parameters from the file
125 The last form is described below.
127 .Bl -tag -width indent
128 .It Fl a Ar temporary-directory
129 Specify an alternative location for the real mount points.
135 in seconds, that a looked up name remains
136 cached when not in use.
137 The default is 5 minutes.
139 Specify the local domain name.
140 If this option is not
141 given the domain name is determined from the hostname.
142 .It Fl k Ar kernel-arch
143 Specifies the kernel architecture.
145 to set the ${karch} selector.
147 Specify a logfile in which to record mount and unmount events.
152 then the log messages will be sent to the system log daemon by
154 The default syslog facility used is
157 wish to change it, append its name to the log file name, delimited by a
165 will log messages via
169 facility (if it exists on the system).
172 The name referred to by ${rhost} is normalized relative to the
173 host database before being used.
174 The effect is to translate
178 .It Fl o Ar op_sys_ver
179 Override the compiled-in version number of the operating system.
181 when the built in version is not desired for backward compatibility reasons.
182 For example, if the build in version is
184 you can override it to
186 and use older maps that were written with the latter in mind.
189 Outputs the process ID of
191 to standard output where it can be saved into a file.
193 Restart existing mounts.
197 will scan the mount file table to determine which file systems
198 are currently mounted.
199 Whenever one of these would have
204 .It Fl t Ar timeout.retransmit
208 in tenths of a second, between
210 retries (for UDP only).
213 The second value alters the retransmit counter, which
214 defaults to 11 retransmissions.
215 Both of these values are used by the kernel
216 to communicate with amd.
217 Useful defaults are supplied if either or both
223 relies on the kernel RPC retransmit mechanism to trigger mount retries.
224 The values of these parameters change the overall retry interval.
226 an interval gives poor interactive response; too short an interval causes
230 Displays version and configuration information on standard error.
234 in seconds, between attempts to dismount
235 file systems that have exceeded their cached times.
236 The default is 2 minutes.
239 Specify run-time logging options. The options are a comma separated
241 .Li fatal, error, user, warn, info, map, stats, defaults, all .
242 Note that "fatal" and "error" are mandatory and cannot be turned off.
245 Specify an alternative
247 domain from which to fetch the
250 The default is the system domain name. This option is ignored if NIS
251 support is not available.
253 Specifies the OS architecture.
254 This is used solely to set the ${arch}
256 .It Fl C Ar cluster-name
257 Specify an alternative HP-UX cluster name to use.
259 Select from a variety of debug options.
261 option with the string
263 reverses the effect of that option.
264 Options are cumulative.
265 The most useful option is
270 is only used for debugging other options are not documented here:
271 the current supported set of options is listed by the
274 and a fuller description is available in the program source.
275 .It Fl F Ar conf_file
278 configuration file to use.
281 for description of this file's format.
282 This configuration file is used to
283 specify any options in lieu of typing many of them on the command line.
286 file includes directives for every command line option amd has, and many
287 more that are only available via the configuration file facility.
289 configuration file specified by this option is processed after all other
290 options had been processed, regardless of the actual location of this option
293 Print help and usage string.
294 .It Fl O Ar op_sys_name
295 Override the compiled-in name of the operating system.
297 built in name is not desired for backward compatibility reasons.
299 example, if the build in name is
301 you can override it to
303 and use older maps which were written with the latter in mind.
305 Do not lock the running executable pages of
310 performance, systems that support the
315 This way there is less chance
316 the operating system will schedule, page out, and swap the
320 This tends to improve
322 performance, at the cost of reserving the
325 process (making it unavailable for other processes).
326 If this behavior is not desired, use the
330 Specify a tag to use with
332 All map entries tagged with
335 Map entries that are not tagged are always processed.
336 Map entries that are tagged with a tag other than
338 will not be processed.
341 .Bl -tag -width ".Pa /etc/amd.conf"
343 directory under which file systems are dynamically mounted
345 default configuration file
348 Some care may be required when creating a mount map.
352 file system can be incredibly inefficient.
353 In most implementations of
355 their interpolations are not cached
356 by the kernel and each time a symbolic link is encountered during a
358 translation it costs an
363 It would appear that a large improvement in real-time
364 performance could be gained by adding a cache somewhere.
365 Replacing symlinks with a suitable incarnation of the auto-mounter
366 results in a large real-time speedup, but also causes a large
367 number of process context switches.
369 A weird imagination is most useful to gain full advantage of all
387 .%B "Linux NFS and Automounter Administration"
388 .%O ISBN 0-7821-2739-8
393 .Pa http://www.am-utils.org/
395 .%T Amd \- The 4.4 BSD Automounter
400 utility first appeared in
403 .An Jan-Simon Pendry Aq jsp@doc.ic.ac.uk ,
404 Department of Computing, Imperial College, London, UK.
406 .An Erez Zadok Aq ezk@cs.sunysb.edu ,
407 Computer Science Department, Stony Brook
408 University, Stony Brook, New York, USA.
410 Other authors and contributors to am-utils are listed in the
412 file distributed with am-utils.