2 .\" Copyright (c) 1997-2006 Erez Zadok
3 .\" Copyright (c) 1990 Jan-Simon Pendry
4 .\" Copyright (c) 1990 Imperial College of Science, Technology & Medicine
5 .\" Copyright (c) 1990 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. All advertising materials mentioning features or use of this software
20 .\" must display the following acknowledgment:
21 .\" This product includes software developed by the University of
22 .\" California, Berkeley and its contributors.
23 .\" 4. Neither the name of the University nor the names of its contributors
24 .\" may be used to endorse or promote products derived from this software
25 .\" without specific prior written permission.
27 .\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
28 .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
29 .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
30 .\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
31 .\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
32 .\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
33 .\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
34 .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
35 .\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
36 .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
39 .\" %W% (Berkeley) %G%
41 .\" $Id: amq.8,v 1.15.2.1 2006/01/02 18:48:24 ezk Exp $
43 .TH AMQ 8 "25 April 1989"
45 amq \- automounter query tool
55 .BI \-x " log_options"
57 .BI \-D " debug_options"
59 .BI \-P " program_number"
67 provides a simple way of determining the current state of
72 Three modes of operation are supported by the current protocol. By default
73 a list of mount points and auto-mounted filesystems is output. An
74 alternative host can be specified using the
80 names are given, as output by default, then per-filesystem
81 information is displayed.
86 Ask the automounter to flush the internal caches and reload all the maps.
90 Specify an alternate host to query. By default the local host is used. In
93 cluster, the root server is queried by default, since that is the system on
94 which the automounter is normally run.
100 as the log file name. For security reasons, this must be the same log file
101 which amd used when started. This option is therefore only useful to
102 refresh amd's open file handle on the log file, so that it can be rotated
103 and compressed via daily cron jobs.
107 Ask the automounter to provide a list of mounted filesystems, including the
108 number of references to each filesystem and any error which occurred while
113 Return the process ID of the remote or locally running amd. Useful when you
114 need to send a signal to the local amd process, and would rather not have to
115 search through the process table. This option is used in the
121 Ask the automounter to provide system-wide mount statistics.
125 Ask the automounter to unmount the filesystems named in
128 information about them. Unmounts are requested, not forced. They merely
129 cause the mounted filesystem to timeout, which will be picked up by
131 main scheduler thus causing the normal timeout action to be taken.
135 Ask the automounter for its version information. This is a subset of the
136 information output by
143 Translate a full pathname as returned by
147 pathname that goes through its mount points. This option requires that
152 .BI \-x " log_options"
153 Ask the automounter to use the logging options specified in
158 .BI \-D " log_options"
159 Ask the automounter to use the debugging options specified in
165 Display short usage message.
168 .BI \-P " program_number"
169 Contact an alternate running amd that had registered itself on a different
172 and apply all other operations to that instance of the automounter. This is
173 useful when you run multiple copies of amd, and need to manage each
174 one separately. If not specified, amq will use the default program number
175 for amd, 300019. For security reasons, the only alternate program numbers
176 amd can use range from 300019 to 300029, inclusive.
182 using the TCP transport only. Normally
184 will try TCP, and if that failed, will try UDP.
190 using UDP (connectionless) transport only. Normally
192 will try TCP, and if that failed, will try UDP.
198 protocol description.
202 uses a Sun registered
204 program number (300019 decimal) which may not
205 be in the /etc/rpc database.
207 If the TCP wrappers library is available, and the
211 option is set to ``yes'', then
213 will verify that the host running
215 is authorized to connect. The
217 service name must used in the
221 files. For example, to allow only localhost to connect to
241 .BR hosts_access (5).
247 .I "Linux NFS and Automounter Administration"
248 by Erez Zadok, ISBN 0-7821-2739-8, (Sybex, 2001).
250 .I http://www.am-utils.org
252 .I "Amd \- The 4.4 BSD Automounter"
255 Jan-Simon Pendry <jsp@doc.ic.ac.uk>, Department of Computing, Imperial College, London, UK.
257 Erez Zadok <ezk@cs.sunysb.edu>, Computer Science Department, Stony Brook
258 University, Stony Brook, New York, USA.
260 Other authors and contributors to am-utils are listed in the
262 file distributed with am-utils.