FIXMOUNT(8L)

NAME
fixmount - fix remote mount entries

SYNOPSIS
/usr/local/etc/fixmount [ -adervq ] [ -h name ] host ...

DESCRIPTION

fixmount is a variant of showmount(8) that can delete bogus mount entries in remote mountd(8C) daemons. The actions specified by the options are performed for each host in turn.

OPTIONS
The -a, -d, and -e options work as in showmount(8) except that only entries pertaining to the local host are printed.

-r  Removes those remote mount entries on host 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 /etc/mtab.

-v  Verify remote mounts. Similar to -r except that only a notification message is printed for each bogus entry found. The remote mount table is not changed.

-q  Be quiet. Suppresses error messages due to timeouts and "Program not registered", i.e., due to remote hosts not supporting RPC or not running mountd.

-h name
    Pretend the local hostname is name. 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 won't be able to successfully handle removal of such entries, so this option is useful in combination with -v only.

FILES
/etc/mtab
    List of current mounts.
/etc/rmtab
    Backup file for remote mount entries on NFS server.

SEE ALSO
showmount(8), mtab(5), rmtab(5), mountd(8C)

BUGS
No attempt is made to verify the information in /etc/mtab itself.

Since swap file mounts are not recorded in /etc/mtab, a heuristic specific to SunOS is used to determine whether such a mount is actual (replacing the string "swap" with "root" and verifying the resulting path).

Symbolic links on the server will cause the path in the remote entry to differ from the one in /etc/mtab. To catch those cases, a filesystem is also deemed mounted if its local mount point is identical to the remote entry. I.e., on a SunOS diskless client, server:/export/share/sunos.4.1.1 is actually /usr/share. Since the local mount point is /usr/share as well this will be handled correctly.