4 .\" Copyright (C) 1999 Olaf Kirch <okir@monad.swb.de>
5 .\" Modified by Jeffrey A. Uphoff, 1999.
6 .\" Modified by Lon Hohberger, 2000.
7 .TH rpc.statd 8 "08 Mar 2001"
9 rpc.statd \- NSM status monitor
11 .B "/sbin/rpc.statd [-F] [-d] [-?] [-n " name "] [-o " port "] [-p " port "] [-V]"
15 server implements the NSM (Network Status Monitor) RPC protocol.
16 This service is somewhat misnomed, since it doesn't actually provide
17 active monitoring as one might suspect; instead, NSM implements a
18 reboot notification service. It is used by the NFS file locking service,
20 to implement lock recovery when the NFS server machine crashes and
23 For each NFS client or server machine to be monitored,
27 When starting, it iterates through these files and notifies the
36 forks and puts itself in the background when started. The
38 argument tells it to remain in the foreground. This option is
39 mainly for debugging purposes.
44 sends logging messages via
48 argument forces it to log verbose output to
50 instead. This option is mainly for debugging purposes, and may only
51 be used in conjunction with the
55 .BI "\-n," "" " \-\-name " name
58 to use as the local hostname. By default,
62 to get the local hostname. Specifying
63 a local hostname may be useful for machines with more than one
66 .BI "\-o," "" " \-\-outgoing\-port " port
69 to send outgoing status requests from. By default,
73 to assign it a port number. As of this writing, there is not
74 a standard port number that
76 always or usually assigns. Specifying
77 a port may be useful when implementing a firewall.
79 .BI "\-p," "" " \-\-port " port
82 to listen on. By default,
86 to assign it a port number. As of this writing, there is not
87 a standard port number that
89 always or usually assigns. Specifying
90 a port may be useful when implementing a firewall.
95 to print out command-line help and exit.
100 to print out version information and exit.
104 .SH TCP_WRAPPERS SUPPORT
107 version is protected by the
109 library. You have to give the clients access to
111 if they should be allowed to use it. To allow connects from clients of
112 the .bar.com domain you could use the following line in /etc/hosts.allow:
116 You have to use the daemon name
118 for the daemon name (even if the binary has a different name).
120 For further information please have a look at the
127 .BR /var/lib/nfs/state
129 .BR /var/lib/nfs/sm/*
131 .BR /var/lib/nfs/sm.bak/*
137 Jeff Uphoff <juphoff@transmeta.com>
139 Olaf Kirch <okir@monad.swb.de>
141 H.J. Lu <hjl@gnu.org>
143 Lon Hohberger <hohberger@missioncriticallinux.com>