This document is a Mac OS X manual page. Manual pages are a command-line technology for providing documentation. You can view these manual pages locally using the man(1) command. These manual pages come from many different sources, and thus, have a variety of writing styles.

For more information about the manual page format, see the manual page for manpages(5).

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

NAME
     rpc.statd -- host status monitoring daemon

SYNOPSIS
     rpc.statd [-d]
     rpc.statd -n

DESCRIPTION
     The rpc.statd utility is a daemon which cooperates with rpc.statd daemons on other hosts to provide a
     status monitoring service.  The daemon accepts requests from programs running on the local host (typi-cally, (typically,
     cally, rpc.lockd(8), the NFS file locking daemon) to monitor the status of specified hosts.  If a moni-tored monitored
     tored host crashes and restarts, the remote daemon will notify the local daemon, which in turn will
     notify the local program(s) which requested the monitoring service.  Conversely, if this host crashes
     and restarts, the statd.notify service will be started to notify all of the hosts which were being mon-itored monitored
     itored at the time of the crash.

     The rpc.statd utility consists of two launchd(8)-controlled services.  The statd.notify service is run
     whenever the system needs to notify remote hosts of a restart.  The statd service is controlled by
     rpc.lockd(8) so that the rpc.statd daemon is running whenever rpc.lockd(8) is running.

     The following is a list of command line options that are available.  However, since rpc.statd is nor-mally normally
     mally started by launchd(8), configuration of these options should be controlled using the equivalent
     settings in the NFS configuration file.  See nfs.conf(5) for a list of tunable parameters.

     -d      Cause debugging information to be written to syslog, recording all RPC transactions to the dae-mon. daemon.
             mon.  These messages are logged with level LOG_DEBUG and facility LOG_DAEMON.  Error conditions
             are logged irrespective of this option, using level LOG_ERR.

     -n      Just send SM_NOTIFY messages to notify any hosts of a restart.  Do not start daemon.

FILES
     /var/db/statd.status       non-volatile record of monitored hosts.
     /var/run/statd.pid         The pid of the current statd daemon.
     /var/run/statd.notify.pid  The pid of the current statd.notify daemon.
     /System/Library/LaunchDaemons/com.apple.statd.notify.plist
                                The statd.notify service's property list file for launchd(8).
     /usr/include/rpcsvc/sm_inter.x
                                RPC protocol specification used by local applications to register monitoring
                                requests.

SEE ALSO
     nfs.conf(5), rpc.lockd(8), syslog(3), launchd(8)

BUGS
     There is no means for the daemon to tell when a monitored host has disappeared permanently (eg. cata-strophic catastrophic
     strophic hardware failure), as opposed to transient failure of the host or an intermediate router.  At
     present, it will re-try 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 relationship.  This is convenient for the NFS locking protocol, but
     probably reduces the usefulness of the monitoring system for other applications.

     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.

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

BSD                             January 9, 2007                            BSD