AMD(8) | MidnightBSD System Manager's Manual | AMD(8) |
amd
—
automatically mount file systems
amd |
-H |
amd |
[-F conf_file] |
amd |
[-nprvHS ] [-a
mount_point] [-c
duration] [-d
domain] [-k
kernel-arch] [-l
logfile] [-o
op_sys_ver] [-t
timeout.retransmit] [-w
interval] [-x
log-option] [-y
YP-domain] [-A
arch] [-C
cluster-name] [-D
option] [-F
conf_file] [-O
op_sys_name] [-T
tag] [directory mapname
[-map-options ]] ... |
amd
daemon in the
FreeBSD base system is deprecated and will be removed
before FreeBSD 13.0. Users are advised to use
autofs(5) or the
sysutils/am-utils port or package instead.The amd
utility is a daemon that
automatically mounts file systems whenever a file or directory within that
file system is accessed. File systems are automatically unmounted when they
appear to be quiescent.
The amd
utility operates by attaching
itself as an NFS server to each of the specified
directories. Lookups within the specified directories
are handled by amd
, which uses the map defined by
mapname to determine how to resolve the lookup.
Generally, this will be a host name, some file system information and some
mount options for the given file system.
In the first form depicted above, amd
will
print a short help string. In the second form, if no options are specified,
or if the -F
is used, amd
will read configuration parameters from the file
conf_file which defaults to
/etc/amd.conf. The last form is described below.
-a
temporary-directory-c
duration-d
domain-k
kernel-arch-l
logfilesyslog
”, then the log messages will
be sent to the system log daemon by
syslog(3). The default
syslog facility used is LOG_DAEMON
. If you wish to
change it, append its name to the log file name, delimited by a single
colon. For example, if logfile is the string
“syslog:local7
” then
amd
will log messages via
syslog(3) using the
LOG_LOCAL7
facility (if it exists on the
system).-n
-o
op_sys_ver2.5.1
”, you can override it to
“5.5.1
”, and use older maps that
were written with the latter in mind.-p
amd
to
standard output where it can be saved into a file.-r
amd
utility will scan
the mount file table to determine which file systems are currently
mounted. Whenever one of these would have been auto-mounted,
amd
inherits
it.-t
timeout.retransmitThe amd(8) utility relies on the kernel RPC retransmit mechanism to trigger mount retries. The values of these parameters change the overall retry interval. Too long an interval gives poor interactive response; too short an interval causes excessive retries.
-v
-w
interval-x
optionsfatal, error, user, warn, info, map, stats,
defaults, all
. Note that "fatal" and "error"
are mandatory and cannot be turned off.-y
domain-A
arch-C
cluster-name-D
optionno
” reverses the effect of
that option. Options are cumulative. The most useful option is
“all
”.
Since -D
is only used for debugging
other options are not documented here: the current supported set of
options is listed by the -v
option and a fuller
description is available in the program source.
-F
conf_fileamd
configuration file to use. See
amd.conf(5) for
description of this file's format. This configuration file is used to
specify any options in lieu of typing many of them on the command line.
The amd.conf(5) file
includes directives for every command line option amd has, and many more
that are only available via the configuration file facility. The
configuration file specified by this option is processed after all other
options had been processed, regardless of the actual location of this
option on the command line.-H
-O
op_sys_namesunos5
”, you can override it to
“sos5
” and use older maps which were
written with the latter in mind.-S
amd
into memory. To improve amd
's performance, systems
that support the
plock(3) call, could
lock the amd
process into memory. This way there
is less chance the operating system will schedule, page out, and swap the
amd
process as needed. This tends to improve
amd
's performance, at the cost of reserving the
memory used by the amd
process (making it
unavailable for other processes). If this behavior is not desired, use the
-S
option.-T
tagSome care may be required when creating a mount map.
Symbolic links on an NFS file system can be incredibly inefficient. In most implementations of NFS, their interpolations are not cached by the kernel and each time a symbolic link is encountered during a lookuppn translation it costs an RPC call to the NFS server. It would appear that a large improvement in real-time performance could be gained by adding a cache somewhere. Replacing symlinks with a suitable incarnation of the auto-mounter results in a large real-time speedup, but also causes a large number of process context switches.
A weird imagination is most useful to gain full advantage of all the features.
domainname(1), hostname(1), syslog(3), amd.conf(5), mtab(5), amq(8), automount(8), mount(8), umount(8)
“am-utils” info(1) entry.
Erez Zadok, Linux NFS and Automounter Administration, Sybex, 2001, ISBN 0-7821-2739-8.
http://www.am-utils.org/
Amd - The 4.4 BSD Automounter.
The amd
utility first appeared in
4.4BSD.
Jan-Simon Pendry ⟨jsp@doc.ic.ac.uk⟩, Department of Computing, Imperial College, London, UK.
Erez Zadok ⟨ezk@cs.sunysb.edu⟩, Computer
Science Department, Stony Brook University, Stony Brook, New York, USA.
Other authors and contributors to am-utils are listed in the AUTHORS file distributed with am-utils.
November 22, 2019 | midnightbsd-3.1 |