NAME
rpc.lockd —
NFS file locking daemon
SYNOPSIS
rpc.lockd |
[-d debug_level]
[-g grace period]
[-h bindip]
[-p port] |
DESCRIPTION
Therpc.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).
Options and operands available for
rpc.lockd:
-d- The
-doption causes debugging information to be written to syslog, recording all RPC transactions to the daemon. These messages are logged with levelLOG_DEBUGand facilityLOG_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 daemon. -g- The
-goption allow to specify the grace period, in seconds. During the grace periodrpc.lockdonly accepts requests from hosts which are reinitialising locks which existed before the server restart. Default is 30 seconds. -hbindip- Specify specific IP addresses to bind to. This option may be specified
multiple times. If no
-hoption is specified,rpc.lockdwill bind toINADDR_ANY. Note that when specifying IP addresses with-h,rpc.lockdwill automatically add127.0.0.1and if IPv6 is enabled,::1to the list. -p- The
-poption allow to force the daemon to bind to the specified port, for both AF_INET and AF_INET6 address families.
Error conditions are logged to syslog, irrespective of the debug
level, using log level LOG_ERR and facility
LOG_DAEMON.
The rpc.lockd 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 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
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.
BUGS
The current implementation provides only the server side of the protocol (i.e., clients running other OS types can establish locks on a DragonFly fileserver, but there is currently no means for a DragonFly client to establish locks).
The current implementation serialises locks requests that could be shared.