4 .\" Copyright (c) 1997-2009 Erez Zadok
5 .\" Copyright (c) 1990 Jan-Simon Pendry
6 .\" Copyright (c) 1990 Imperial College of Science, Technology & Medicine
7 .\" Copyright (c) 1990 The Regents of the University of California.
8 .\" All rights reserved.
10 .\" This code is derived from software contributed to Berkeley by
11 .\" Jan-Simon Pendry at Imperial College, London.
13 .\" Redistribution and use in source and binary forms, with or without
14 .\" modification, are permitted provided that the following conditions
16 .\" 1. Redistributions of source code must retain the above copyright
17 .\" notice, this list of conditions and the following disclaimer.
18 .\" 2. Redistributions in binary form must reproduce the above copyright
19 .\" notice, this list of conditions and the following disclaimer in the
20 .\" documentation and/or other materials provided with the distribution.
21 .\" 3. All advertising materials mentioning features or use of this software
22 .\" must display the following acknowledgment:
23 .\" This product includes software developed by the University of
24 .\" California, Berkeley and its contributors.
25 .\" 4. Neither the name of the University nor the names of its contributors
26 .\" may be used to endorse or promote products derived from this software
27 .\" without specific prior written permission.
29 .\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
30 .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
31 .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
32 .\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
33 .\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
34 .\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
35 .\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
36 .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
37 .\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
38 .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
42 .\" File: am-utils/fixmount/fixmount.8
44 .TH FIXMOUNT 8 "26 Feb 1993"
46 fixmount \- fix remote mount entries
59 .IX "fixmount command" "" "\fLfixmount\fP \(em fix remote mount entries"
64 that can delete bogus mount entries in remote
67 The actions specified by the options are performed for each
73 These options work as in
75 except that only entries pertaining to the local host are printed.
78 Removes those remote mount entries on
80 that do not correspond to current mounts, i.e., which are left-over
81 from a crash or are the result of improper mount protocol.
82 The actuality of mounts is verified using the entries in
86 Verify remote mounts. Similar to
88 except that only a notification message is printed for each bogus entry
89 found. The remote mount table is not changed.
92 Issues a command to the remote mountd declaring that ALL of its filesystems
93 have been unmounted. This should be used with caution, as it removes all
94 remote mount entries pertaining to the local system, whether or not any
95 filesystems are still mounted locally.
99 Suppresses error messages due to timeouts and "Program not registered",
100 i.e., due to remote hosts not supporting RPC or not running mountd.
103 Pretend the local hostname is
105 This is useful after the local hostname has been changed and rmtab entries
106 using the old name remain on a remote machine.
107 Unfortunately, most mountd's won't be able to successfully handle removal
108 of such entries, so this option is useful in combination with
112 This option also saves time as comparisons of remotely recorded and local
113 hostnames by address are avoided.
117 List of current mounts.
120 Backup file for remote mount entries on NFS server.
131 .I "Linux NFS and Automounter Administration"
132 by Erez Zadok, ISBN 0-7821-2739-8, (Sybex, 2001).
134 .I http://www.am-utils.org
136 .I "Amd \- The 4.4 BSD Automounter"
138 No attempt is made to verify the information in
142 Since swap file mounts are not recorded in
144 a heuristic specific to SunOS is used to determine whether such a mount
145 is actual (replacing the string "swap" with "root" and verifying the resulting
148 Symbolic links on the server will cause the path in the remote entry to differ
151 To catch those cases, a filesystem is also deemed mounted if its
153 mount point is identical to the remote entry.
154 I.e., on a SunOS diskless client,
155 .B server:/export/share/sunos.4.1.1
158 Since the local mount point is
160 as well this will be handled correctly.
162 There is no way to clear a stale entry in a remote mountd after the
163 local hostname (or whatever reverse name resolution returns for it)
164 has been changed. To take care of these cases,
165 the remote /etc/rmtab file has to be edited and mountd restarted.
167 The RPC timeouts for mountd calls can only be changed by recompiling.
168 The defaults are 2 seconds for client handle creation and 5 seconds for
171 Andreas Stolcke <stolcke@icsi.berkeley.edu>.
173 Erez Zadok <ezk@cs.sunysb.edu>, Computer Science Department, Stony Brook
174 University, Stony Brook, New York, USA.
176 Other authors and contributors to am-utils are listed in the
178 file distributed with am-utils.