Home Man
Today's Posts

Linux & Unix Commands - Search Man Pages
Man Page or Keyword Search:
Select Section of Man Page:
Select Man Page Repository:

NetBSD 6.1.5 - man page for rpc.lockd (netbsd section 8)

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

     rpc.lockd -- NFS file locking daemon

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

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

     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.

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

     syslog(3), rc.conf(5), rpc.statd(8)

     The implementation is based on the specification in X/Open CAE Specification C218, "Proto-
     cols for X/Open PC Interworking: XNFS, Issue 4", ISBN 1 872630 66 9

     A version of rpc.lockd appeared in SunOS 4.

     The current implementation provides only the server side of the protocol (i.e. clients run-
     ning 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

All times are GMT -4. The time now is 05:06 AM.

Unix & Linux Forums Content Copyrightę1993-2018. All Rights Reserved.
Show Password