2 .\" Copyright (c) 1997-1999 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: fixmount.8,v 1.2 1999/01/10 21:54:26 ezk Exp $
42 .\" $FreeBSD: src/contrib/amd/fixmount/fixmount.8,v 1.5.2.2 2001/03/06 16:54:05 ru Exp $
49 .Nd fix remote mount entries
60 that can delete bogus mount entries in remote
62 daemons. The actions specified by the options are performed for each
68 These options work as in
70 except that only entries pertaining to the local host are printed.
72 Removes those remote mount entries on
74 that do not correspond to current mounts, i.e., which are left-over
75 from a crash or are the result of improper mount protocol.
76 The actuality of mounts is verified using the entries in
79 Verify remote mounts. Similar to
81 except that only a notification message is printed for each bogus entry
82 found. The remote mount table is not changed.
84 Issues a command to the remote mountd declaring that
86 of its filesystems have been unmounted. This should be used with caution, as
87 it removes all remote mount entries pertaining to the local system, whether or
88 not any filesystems are still mounted locally.
90 Be quiet. Suppresses error messages due to timeouts and
91 .Dq Program not Registered ,
92 i.e., due to remote hosts not supporting RPC or not running
95 Pretend the local hostname is
97 This is useful after the local hostname has been changed and rmtab entries
98 using the old name remain on a remote machine.
99 Unfortunately, most mountd's won't be able to successfully handle removal
100 of such entries, so this option is useful in combination with
104 This option also saves time as comparisons of remotely recorded and local
105 hostnames by address are avoided.
110 List of current mounts.
112 Backup file for remote mount entries on
122 No attempt is made to verify the information in
126 Since swap file mounts are not recorded in
128 a heuristic specific to SunOS is used to determine whether such a mount
129 is actual (replacing the string
133 and verifying the resulting path).
135 Symbolic links on the server will cause the path in the remote entry to differ
138 To catch those cases, a filesystem is also deemed mounted if its
140 mount point is identical to the remote entry.
141 I.e., on a SunOS diskless client,
142 .Pa server:/export/share/sunos.4.1.1
145 Since the local mount point is
147 as well this will be handled correctly.
149 There is no way to clear a stale entry in a remote
151 after the local hostname (or whatever reverse name resolution
152 returns for it) has been changed. To take care of these cases,
155 file has to be edited and
161 calls can only be changed by recompiling. The defaults are 2 seconds
162 for client handle creation and 5 seconds for RPC calls.
164 .An Jan-Simon Pendry Aq jsp@doc.ic.ac.uk ,
165 Department of Computing, Imperial College, London, UK.
167 .An Erez Zadok Aq ezk@cs.columbia.edu ,
168 Department of Computer Science, Columbia University, New York, USA.
170 .An Other authors and contributors to
174 file distributed with