Mac Developer Library Developer


This manual page is for Mac OS X version 10.9

If you are running a different version of Mac OS X, view the documentation locally:

  • In Terminal, using the man(1) command

Reading manual pages

Manual pages are intended as a quick reference for people who already understand a technology.

  • To learn how the manual is organized or to learn about command syntax, read the manual page for manpages(5).

  • For more information about this technology, look for other documentation in the Apple Developer Library.

  • For general information about writing shell scripts, read Shell Scripting Primer.

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

     rpc.statd -- host status monitoring daemon

     rpc.statd [-d]
     rpc.statd [-d] -n
     rpc.statd [-d] [-l | -L | -N hostname]

     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.  Note that 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      Sets the logging level to the maximum.  Note that finer grain control is available via the
             nfs.statd.verbose option in nfs.conf(5).

             Logging is performed via syslog(3) using the LOG_DAEMON facility.  By default, only messages up
             to priority LOG_WARNING are logged.  Setting the verbose level to one will add LOG_NOTICE mes-sages messages
             sages which includes logging failed mount attempts.  A verbose level of two will increase the
             log level to LOG_INFO which includes logging successful mount attempts.  A log level of three
             or more will add LOG_DEBUG messages and cause increasing amounts of debug information to be
             logged.  The debug information exposes lots of information about rpc.statd's inner workings
             which is typically only useful to developers.  Note: the syslog(8) configuration may need to be
             adjusted in order to see the increased verbosity.

     The following command line option causes the daemon to run in the statd.notify notification service

     -n      Send SM_NOTIFY messages to notify any hosts of a restart.

     The remaining command line options may be useful for viewing or modifying the contents of the status
     file.  They do not start up any daemon or service.

     -l      List each host (and its status) in the status file.

     -L      List each host (and its status) in the status file and then continue to watch the file and
             report changes.

     -N      Clear the "needs notification" status for hostname so the statd.notify service will no longer
             try to notify it.

     /var/db/statd.status       non-volatile record of monitored hosts.
     /var/run/         The pid of the current statd daemon.
     /var/run/  The pid of the current statd.notify daemon.
                                The statd.notify service's property list file for launchd(8).
                                RPC protocol specification used by local applications to register monitoring

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

     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 pause and re-try notification at frequent intervals for 10 minutes, then hourly, and
     finally gives up after 24 hours.  The -N option may be used to remove the "needs notification" status
     from such hosts.

     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 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                              July 5, 2008                              BSD

Reporting Problems

The way to report a problem with this manual page depends on the type of problem:

Content errors
Report errors in the content of this documentation with the feedback links below.
Bug reports
Report bugs in the functionality of the described tool or API through Bug Reporter.
Formatting problems
Report formatting mistakes in the online version of these pages with the feedback links below.