rpc.statd(8) [opendarwin 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

     The rpc.statd utility 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 program(s) which requested the monitoring service.  Conversely, if this host crashes and re-starts, when the rpc.statd re-starts, it
     will notify all of the hosts which were being monitored at the time of the crash.

     The following option is available:

     -d      Cause 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.

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

     The rpc.statd utility must NOT be invoked by inetd(8) because the protocol assumes that the daemon will run from system start time.  Instead,
     it should be run from rc(8) after the network has been started.

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(8), rpc.lockd(8)

BUGS

     There is no means for the daemon to tell when a monitored host has disappeared permanently (eg. catastrophic 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 min-
     utes, 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.

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
								September 19, 1995							       BSD

Check Out this Related Man Page

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

NAME

     rpc.lockd -- NFS file locking daemon

SYNOPSIS

     rpc.lockd [-d debug_level] [-g grace period]

DESCRIPTION

     The rpc.lockd daemon provides monitored and unmonitored file and record locking services in an NFS environment.  To monitor the status of
     hosts requesting locks, the locking daemon typically operates in conjunction with rpc.statd(8).

     Options and operands available for rpc.lockd :

     -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.  Specifying a debug_level of 1 results in the generation of one log line per
	     protocol operation.  Higher debug levels can be specified, causing display of operation arguments and internal operations of the dae-
	     mon.

     -g      The -g option allow to specify the grace period, in seconds. During the grace period rpc.lockd only accepts requests from hosts which
	     are reinitialising locks which existed before the server restart. Default is 30 seconds.

     Error conditions are logged to syslog, irrespective of the debug level, using log level LOG_ERR and facility LOG_DAEMON.

     The rpc.lockd 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

     /usr/include/rpcsvc/nlm_prot.x  RPC protocol specification for the network lock manager protocol.

SEE ALSO

     syslog(3), rc.conf(5), rpc.statd(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.lockd appeared in SunOS 4.

BUGS

     The current implementation provides only the server side of the protocol (i.e. clients running other OS types can establish locks on a NetBSD
     fileserver, but there is currently no means for a NetBSD client to establish locks).

     The current implementation serialises locks requests that could be shared.

BSD
								September 24, 1995							       BSD

Linux and UNIX Man Pages

rpc.statd(8) [opendarwin man page]

Check Out this Related Man Page