rpc.lockd(8) [osf1 man page]

rpc.lockd(8)						      System Manager's Manual						      rpc.lockd(8)

NAME

       rpc.lockd, lockd - Network lock daemon

SYNOPSIS

       /usr/sbin/rpc.lockd [-b hostname] [-c] [-d debug] [-g graceperiod] [-h hashsize] [-s] [-t timeout]

OPTIONS

       The  default  behavior  will  create  and bind a socket for each protocol per interface on the system. When the -b switch is specified, one
       socket per protocol will be created and bind to the passed IP address.  Available only on TruCluster Server systems. This option starts the
       clusterwide lock daemon, which helps provide highly available NFS service. Do not use -c directly.  Highly available NFS service is config-
       ured by default and typically does not require intervention. If you do need to start the clusterwide lock  daemon,  use	the  CAA  command,
       caa_start cluster_lockd.

	      For more information, see the TruCluster Server Administration manual.  Internal Use Only.  Use this option only under the direction
	      of technical support personnel.  Causes the rpc.lockd daemon to use the variable graceperiod (in seconds) as the grace period  dura-
	      tion  instead  of  the default value of 15 seconds.  Internal Use Only.  Causes the rpc.lockd daemon to use the variable timeout (in
	      seconds) as the interval instead of the default value of 5 seconds to retransmit a lock request to the remote server.

DESCRIPTION

       The rpc.lockd daemon processes lock requests that are either sent locally by the kernel or remotely by another lock daemon. The NFS locking
       service makes this advisory locking support possible by using the fcntl system call and the lockf subroutine. The rpc.lockd daemon forwards
       lock requests for remote data to the server site's lock daemon. The rpc.lockd daemon then requests the status  monitor  daemon,	rpc.statd,
       for monitor service. The reply to the lock request is not sent to the kernel until the status daemon and the server site's lock daemon have
       replied.

       If either the status monitor or server site's lock daemon is unavailable, the reply to a lock request for remote data is delayed until  all
       daemons become available.

       When  a server recovers, it waits for a grace period for all client site lock daemons to submit reclaim requests.  Client site lock daemons
       are notified by rpc.statd of the server recovery and promptly resubmit previously granted lock requests.  If a client  site's  lock  daemon
       fails  to secure previously granted locks at the server site, it sends the signal SIGLOST to all the processes that were previously holding
       locks and cannot reclaim them.

SEE ALSO

       Commands: rpc.statd(8)

       Functions: fcntl(2), signal(2), lockf(3)

																      rpc.lockd(8)

lockd(1M)																 lockd(1M)

NAME

       lockd: rpc.lockd - network lock daemon

SYNOPSIS

       graceperiod] listen_min_backlog] timeout] [nthreads]

DESCRIPTION

       The  lockd  utility  is	part of the NFS lock manager, which supports record lock and share lock operations on NFS files.  See fcntl(2) and
       lockf(2).  provides two functions:

	      o  It forwards locking requests for NFS mounted file systems to the lockd on the NFS server.

	      o  It generates local file locking operations in response to requests forwarded from running on NFS client machines.

	      State information kept by the lockd about these locking requests can be lost if is killed or the operating system is rebooted.  Some
	      of  this	information  can  be recovered as follows.  When a server recovers, it waits for a grace period for all NFS client-site to
	      submit reclaim requests.	Client-site is notified by the of the server recovery, and  promptly  resubmits  previously  granted  lock
	      requests.  If a fails to secure a previously granted lock at the server site, then the sends a to the process holding that lock.

	      Administrators  can make changes to the startup parameters for by logging in as root and editing the file (see nfs(4)).  Administra-
	      tors can also make changes by using the command.

   Options
       recognizes the following options and command-line arguments:

	      Deprecated in favor of the
				parameter in the NFS default file, which is equivalent.  Specify the number of seconds that all clients (both  NLM
				and  NFSv4)  have  to reclaim locks after the server reboots.  This option also controls the NFSv4 lease interval.
				The default value is 90 seconds.

	      Specify the listener backlog,
				listen_min_backlog, which is the number of connect requests that are queued and waiting to be processed before new
				connect requests begin to get dropped.

	      Specify the number of seconds to wait before retransmitting a lock
				request  to  the  remote  server.  The default value is 5 seconds.  Equivalent to the parameter in the NFS default
				file.

	      nthreads		Specify the maximum number of concurrent threads that the server can handle.  This concurrency is achieved  by	up
				to  nthreads  threads  created	as  needed  in	the kernel.  nthreads should be based on the load expected on this
				server.  If nthreads is not specified, the maximum number of concurrent threads will default to 20.  Equivalent to
				the parameter in the NFS default file.

   Notes
       A directory service that provides service name data base support must have the following service entries in its database:

       Kernel Lock Manager logging can be enabled using By default, the variable is 0 which disables the Kernel Lock Manager logging feature.  The
       maximum value is 9.  The value determines how detailed the log messages are.

AUTHOR

       was developed by Sun Microsystems, Inc. and HP.

SEE ALSO

       clear_locks(1M), kctune(1M), setoncenv(1M), statd(1M),  fcntl(2),  lockf(2),  signal(2),  getservent(3N),  nfs(4),  nsswitch.conf(4),  ser-
       vices(4).

																	 lockd(1M)