1.\" -*- nroff -*- 2.\" 3.\" Copyright (c) 1995 A.R.Gordon, andrew.gordon@net-tel.co.uk 4.\" All rights reserved. 5.\" 6.\" Redistribution and use in source and binary forms, with or without 7.\" modification, are permitted provided that the following conditions 8.\" are met: 9.\" 1. Redistributions of source code must retain the above copyright 10.\" notice, this list of conditions and the following disclaimer. 11.\" 2. Redistributions in binary form must reproduce the above copyright 12.\" notice, this list of conditions and the following disclaimer in the 13.\" documentation and/or other materials provided with the distribution. 14.\" 3. All advertising materials mentioning features or use of this software 15.\" must display the following acknowledgement: 16.\" This product includes software developed by the University of 17.\" California, Berkeley and its contributors. 18.\" 4. Neither the name of the University nor the names of its contributors 19.\" may be used to endorse or promote products derived from this software 20.\" without specific prior written permission. 21.\" 22.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND 23.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE 24.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE 25.\" ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE 26.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL 27.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS 28.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) 29.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT 30.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY 31.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF 32.\" SUCH DAMAGE. 33.\" 34.\" 35.Dd September 19, 1995 36.Dt RPC.STATD 8 37.Os 38.Sh NAME 39.Nm rpc.statd 40.Nd host status monitoring daemon 41.Sh SYNOPSIS 42.Nm rpc.statd 43.Op Fl d 44.Sh DESCRIPTION 45.Nm Rpc.statd 46is a daemon which co-operates with rpc.statd daemons on other hosts to provide 47a status monitoring service. The daemon accepts requests from 48programs running on the local host (typically, 49.Xr rpc.lockd 8 , 50the NFS file locking daemon) to monitor the status of specified 51hosts. If a monitored host crashes and restarts, the remote daemon will 52notify the local daemon, which in turn will notify the local program(s) 53which requested the monitoring service. Conversely, if this host crashes 54and re-starts, when the 55.Nm 56re-starts, it will notify all of the hosts which were being monitored 57at the time of the crash. 58.Pp 59The following option is available: 60.Bl -tag -width indent 61.It Fl d 62Cause debugging information to be written to syslog, recording 63all RPC transactions to the daemon. These messages are logged with level 64LOG_DEBUG and facility LOG_DAEMON. Error conditions are logged irrespective 65of this option, using level LOG_ERR. 66.El 67.Pp 68The 69.Nm 70daemon must NOT be invoked by 71.Xr inetd 8 72because the protocol assumes that the daemon will run from system start time. 73Instead, it should be run from 74.Xr rc 8 75after the network has been started. 76.Sh FILES 77.Bl -tag -width /usr/include/rpcsvc/sm_inter.x -compact 78.It Pa /var/db/statd.status 79non-volatile record of currently monitored hosts. 80.It Pa /usr/include/rpcsvc/sm_inter.x 81RPC protocol specification used by local applications to register monitoring requests. 82.El 83.Sh SEE ALSO 84.Xr syslog 3 , 85.Xr rc 8 , 86.Xr rpc.lockd 8 87.Sh BUGS 88There is no means for the daemon to tell when a monitored host has 89disappeared permanently (eg. catastrophic hardware failure), as opposed 90to transient failure of the host or an intermediate router. At present, 91it will re-try notification attempts at frequent intervals for 10 minutes, 92then hourly, and finally gives up after 24 hours. 93 94The protocol requires that symmetric monitor requests are made to both 95the local and remote daemon in order to establish a monitored relationship. 96This is convenient for the NFS locking protocol, but probably reduces the 97usefulness of the monitoring system for other applications. 98 99The current implementation uses more than 1Kbyte per monitored host in 100the status file (and also in VM). This may be inefficient for NFS servers 101with large numbers of clients. 102.Sh STANDARDS 103The implementation is based on the specification in X/Open CAE Specification 104C218, "Protocols for X/Open PC Interworking: XNFS, Issue 4", ISBN 1 872630 66 9 105