rpc.lockd — NFS file locking daemon


rpc.lockd [-d debug_level] [-g grace period] [-x statd cache period]


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).

Options and operands available for rpc.lockd:

-d The -d option causes debugging information to be written to sys-
log, recording all RPC transactions to the daemon. These mes-
sages 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 daemon.

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

-w The -w option tells rpc.lockd to wait until the first client
locking request is made before starting the locking daemon(s).
This may be used on NFS clients to defer starting the NFS locking
daemons until it is known that they will be needed. (Note:
rpc.statd(8) will also be started if it isn’t already running)

-x The -x option tells rpc.lockd how long to cache state records for
contacting client rpc.statd(8) implementations. Setting it to
zero will disable the cache which will make lock and unlock
requests from a single client more expensive because of addi-
tional 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.

The rpc.lockd utility must NOT be invoked by inetd(8) because the proto-
col assumes that the daemon will run from system start time. Instead, it
should be configured in rc.conf(5) to run at system startup.


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


Share this post from Rbcafe :
Share on FacebookTweet about this on TwitterPin on PinterestShare on Google+Share on LinkedInEmail this to someoneShare on RedditBuffer this page
Rbcafe © 2004- | Rb Cafe 1.3 | Contatto Rbcafe | Rbcafe su Twitter | Rbcafe su Facebook | Politica sulla riservatezza