4 .\" Copyright (C) 1999 Olaf Kirch <okir@monad.swb.de>
5 .\" Modified by Jeffrey A. Uphoff, 1999, 2002, 2005.
6 .\" Modified by Lon Hohberger, 2000.
7 .\" Modified by Paul Clements, 2004.
8 .TH rpc.statd 8 "31 Aug 2004"
10 rpc.statd \- NSM status monitor
12 .B "rpc.statd [-FNL] [-d] [-?] [-n " name "] [-o " port "] [-p " port "] [-H " prog "] [-V]"
16 server implements the NSM (Network Status Monitor) RPC protocol.
17 This service is somewhat misnamed, since it doesn't actually provide
18 active monitoring as one might suspect; instead, NSM implements a
19 reboot notification service. It is used by the NFS file locking service,
21 to implement lock recovery when the NFS server machine crashes and
24 For each NFS client or server machine to be monitored,
28 When starting, it normally runs
30 to iterate through these files and notify the
39 forks and puts itself in the background when started. The
41 argument tells it to remain in the foreground. This option is
42 mainly for debugging purposes.
47 sends logging messages via
51 argument forces it to log verbose output to
53 instead. This option is mainly for debugging purposes, and may only
54 be used in conjunction with the
58 .BI "\-n," "" " \-\-name " name
61 to use as the local hostname. By default,
65 to get the local hostname. Specifying
66 a local hostname may be useful for machines with more than one
69 .BI "\-o," "" " \-\-outgoing\-port " port
72 to send outgoing status requests from. By default,
76 to assign it a port number. As of this writing, there is not
77 a standard port number that
79 always or usually assigns. Specifying
80 a port may be useful when implementing a firewall.
82 .BI "\-p," "" " \-\-port " port
85 to listen on. By default,
89 to assign it a port number. As of this writing, there is not
90 a standard port number that
92 always or usually assigns. Specifying
93 a port may be useful when implementing a firewall.
95 .BI "\-P," "" " \-\-state\-directory\-path " directory
96 specify a directory in which to place statd state information.
97 If this option is not specified the default of
102 Causes statd to run in the notify-only mode. When started in this mode, the
103 statd program will check its state directory, send notifications to any
104 monitored nodes, and exit once the notifications have been sent. This mode is
105 used to enable Highly Available NFS implementations (i.e. HA-NFS).
106 This mode is deprecated \-
108 should be used directly instead.
110 .BR -L , " --no-notify
111 Inhibits the running of
115 is run by some other script at boot time, there is no need for
117 to start sm-notify itself. This can be appropriate if starting of
118 statd needs to be delayed until it is actually need. In such cases
120 should still be run at boot time.
122 .BI "\-H, " "" " \-\-ha-callout " prog
123 Specify a high availability callout program, which will receive callouts
124 for all client monitor and unmonitor requests. This allows
126 to be used in a High Availability NFS (HA-NFS) environment. The
127 program will be run with 3 arguments: The first is either
131 depending on the reason for the callout.
132 The second will be the name of the client.
133 The third will be the name of the server as known to the client.
138 to print out command-line help and exit.
143 to print out version information and exit.
147 .SH TCP_WRAPPERS SUPPORT
150 version is protected by the
152 library. You have to give the clients access to
154 if they should be allowed to use it. To allow connects from clients of
155 the .bar.com domain you could use the following line in /etc/hosts.allow:
159 You have to use the daemon name
161 for the daemon name (even if the binary has a different name).
163 For further information please have a look at the
173 to re-read the notify list from disk
174 and send notifications to clients. This can be used in High Availability NFS
175 (HA-NFS) environments to notify clients to reacquire file locks upon takeover
176 of an NFS export from another server.
179 .BR /var/lib/nfs/state
181 .BR /var/lib/nfs/sm/*
183 .BR /var/lib/nfs/sm.bak/*
189 Jeff Uphoff <juphoff@users.sourceforge.net>
191 Olaf Kirch <okir@monad.swb.de>
193 H.J. Lu <hjl@gnu.org>
195 Lon Hohberger <hohberger@missioncriticallinux.com>
197 Paul Clements <paul.clements@steeleye.com>