Интерактивная система просмотра системных руководств (man-ов)
>> fixmount (8) ( FreeBSD man: Команды системного администрирования )
fixmount (8) ( Linux man: Команды системного администрирования )
- fix remote mount entries
is a variant of
that can delete bogus mount entries in remote
The actions specified by the options are performed for each
-a , d , e
These options work as in
except that only entries pertaining to the local host are printed.
Removes those remote mount entries on
that do not correspond to current mounts, i.e., which are left-over
from a crash or are the result of improper mount protocol.
The actuality of mounts is verified using the entries in
Verify remote mounts.
except that only a notification message is printed for each bogus entry
The remote mount table is not changed.
Issues a command to the remote mountd declaring that
of its file systems have been unmounted.
This should be used with caution, as it removes all
remote mount entries pertaining to the local system, whether or not any
file systems are still mounted locally.
Suppresses error messages due to timeouts and
``Program not registered
i.e., due to remote hosts not supporting RPC or not running
Pretend the local hostname is
This is useful after the local hostname has been changed and rmtab entries
using the old name remain on a remote machine.
Unfortunately, most mountd's will not be able to successfully handle removal
of such entries, so this option is useful in combination with
This option also saves time as comparisons of remotely recorded and local
hostnames by address are avoided.
List of current mounts.
Backup file for remote mount entries on
An Erez Zadok Aq email@example.com ,
Computer Science Department, Stony Brook University, Stony Brook, New York, USA.
Other authors and contributors to am-utils are listed in the
file distributed with am-utils.
No attempt is made to verify the information in
Since swap file mounts are not recorded in
a heuristic specific to SunOS is used to determine whether such a mount
is actual (replacing the string
and verifying the resulting path).
Symbolic links on the server will cause the path in the remote entry to differ
from the one in
To catch those cases, a file system is also deemed mounted if its
mount point is identical to the remote entry.
I.e., on a SunOS diskless client,
Since the local mount point is
as well this will be handled correctly.
There is no way to clear a stale entry in a remote
local hostname (or whatever reverse name resolution returns for it)
has been changed.
To take care of these cases,
file has to be edited and
The RPC timeouts for
calls can only be changed by recompiling.
The defaults are 2 seconds for client handle creation and 5 seconds for