Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

rpc.lockd(8) [osx man page]

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

rpc.lockd -- NFS file locking daemon SYNOPSIS
rpc.lockd [-d debug_level] [-g grace_period] [-x host_monitor_cache_period] DESCRIPTION
The rpc.lockd utility 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). The rpc.lockd utility runs whenever its services are needed to support either the NFS server (see nfsd(8)) or the NFS client (an NFS file system on which file locking requests have been made). The daemon will remain running until a short time after its services are no longer needed to support either the NFS client or NFS server. rpc.lockd will also make sure that the statd service (on which it depends) is run- ning. The following is a list of command line options that are available. However, since rpc.lockd is normally started by launchd(8), configura- tion of these options should be controlled using the equivalent settings in the NFS configuration file. See nfs.conf(5) for a list of tun- able parameters. -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 allows 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 45 seconds. -x The -x option tells rpc.lockd how long to cache state records for monitored hosts. Setting it to zero will disable the cache which will make lock and unlock requests from a single client more expensive because of additional interaction with the client's statd. The default cache time is 60 seconds. Error conditions are logged to syslog, irrespective of the debug level, using log level LOG_ERR and facility LOG_DAEMON. FILES
/var/run/ The pid of the current lockd daemon. /System/Library/LaunchDaemons/ The lockd service's property list file for launchd(8). /usr/include/rpcsvc/nlm_prot.x RPC protocol specification for the network lock manager protocol. SEE ALSO
nfs.conf(5), rpc.statd(8), syslog(3), launchd(8) BUGS
The current implementation serialises locks requests that could be shared. STANDARDS
The implementation is based on the specification in "Protocols for X/Open PC Interworking: XNFS, Issue 4", X/Open CAE Specification C218, ISBN 1 872630 66 9. HISTORY
A version of rpc.lockd appeared in SunOS 4. BSD
January 9, 2007 BSD

Check Out this Related Man Page

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

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

Featured Tech Videos