Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

statd(8) [redhat man page]

rpc.statd(8)						      System Manager's Manual						      rpc.statd(8)

NAME
rpc.statd - NSM status monitor SYNOPSIS
/sbin/rpc.statd [-F] [-d] [-?] [-n name ] [-o port ] [-p port ] [-V] DESCRIPTION
The rpc.statd server implements the NSM (Network Status Monitor) RPC protocol. This service is somewhat misnomed, since it doesn't actu- ally provide active monitoring as one might suspect; instead, NSM implements a reboot notification service. It is used by the NFS file locking service, rpc.lockd, to implement lock recovery when the NFS server machine crashes and reboots. Operation For each NFS client or server machine to be monitored, rpc.statd creates a file in /var/lib/nfs/statd/sm. When starting, it iterates through these files and notifies the peer rpc.statd on those machines. OPTIONS
-F By default, rpc.statd forks and puts itself in the background when started. The -F argument tells it to remain in the foreground. This option is mainly for debugging purposes. -d By default, rpc.statd sends logging messages via syslog(3) to system log. The -d argument forces it to log verbose output to stderr instead. This option is mainly for debugging purposes, and may only be used in conjunction with the -F parameter. -n, --name name specify a name for rpc.statd to use as the local hostname. By default, rpc.statd will call gethostname(2) to get the local hostname. Specifying a local hostname may be useful for machines with more than one interfaces. -o, --outgoing-port port specify a port for rpc.statd to send outgoing status requests from. By default, rpc.statd will ask portmap(8) to assign it a port number. As of this writing, there is not a standard port number that portmap always or usually assigns. Specifying a port may be useful when implementing a firewall. -p, --port port specify a port for rpc.statd to listen on. By default, rpc.statd will ask portmap(8) to assign it a port number. As of this writ- ing, there is not a standard port number that portmap always or usually assigns. Specifying a port may be useful when implementing a firewall. -? Causes rpc.statd to print out command-line help and exit. -V Causes rpc.statd to print out version information and exit. TCP_WRAPPERS SUPPORT This rpc.statd version is protected by the tcp_wrapper library. You have to give the clients access to rpc.statd if they should be allowed to use it. To allow connects from clients of the .bar.com domain you could use the following line in /etc/hosts.allow: statd: .bar.com You have to use the daemon name statd for the daemon name (even if the binary has a different name). For further information please have a look at the tcpd(8) and hosts_access(5) manual pages. FILES
/var/lib/nfs/statd/sm/state /var/lib/nfs/statd/sm/* /var/lib/nfs/statd/sm.bak/* SEE ALSO
rpc.nfsd(8), portmap(8) AUTHORS
Jeff Uphoff <juphoff@transmeta.com> Olaf Kirch <okir@monad.swb.de> H.J. Lu <hjl@gnu.org> Lon Hohberger <hohberger@missioncriticallinux.com> 08 Mar 2001 rpc.statd(8)

Check Out this Related Man Page

RPC.STATD(8)						    BSD System Manager's Manual 					      RPC.STATD(8)

NAME
rpc.statd -- host status monitoring daemon SYNOPSIS
rpc.statd [-d] DESCRIPTION
rpc.statd is a daemon which co-operates with rpc.statd daemons on other hosts to provide a status monitoring service. The daemon accepts requests from programs running on the local host (typically, rpc.lockd(8), the NFS file locking daemon) to monitor the status of specified hosts. If a monitored host crashes and restarts, the remote daemon will notify the local daemon, which in turn will notify the local pro- gram(s) which requested the monitoring service. Conversely, if this host crashes and restarts, when rpc.statd restarts, it will notify all of the hosts which were being monitored at the time of the crash. Options and operands available for rpc.statd : -d The -d option causes debugging information to be written to syslog, recording all RPC transactions to the daemon. These messages are logged with level LOG_DEBUG and facility LOG_DAEMON. Error conditions are logged irrespective of this option, using level LOG_ERR. The rpc.statd daemon must NOT be invoked by inetd(8) because the protocol assumes that the daemon will run from system start time. Instead, it should be configured in rc.conf(5) to run at system startup. FILES
/var/db/statd.status non-volatile record of currently monitored hosts. /usr/include/rpcsvc/sm_inter.x RPC protocol specification used by local applications to register monitoring requests. SEE ALSO
syslog(3), rc.conf(5), rpc.lockd(8) STANDARDS
The implementation is based on the specification in X/Open CAE Specification C218, "Protocols for X/Open PC Interworking: XNFS, Issue 4", ISBN 1 872630 66 9 HISTORY
A version of rpc.statd appeared in SunOS 4. BUGS
There is no means for the daemon to tell when a monitored host has disappeared permanently (e.g., catastrophic hardware failure), as opposed to transient failure of the host or an intermediate router. At present, it will retry notification attempts at frequent intervals for 10 minutes, then hourly, and finally gives up after 24 hours. The protocol requires that symmetric monitor requests are made to both the local and remote daemon in order to establish a monitored rela- tionship. This is convenient for the NFS locking protocol, but probably reduces the usefulness of the monitoring system for other applica- tions. The current implementation uses more than 1Kbyte per monitored host in the status file (and also in VM). This may be inefficient for NFS servers with large numbers of clients. BSD
September 19, 1995 BSD
Man Page