Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

rpc.lockd(8) [osf1 man page]

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

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)

Check Out this Related Man Page

lockd(1M)						  System Administration Commands						 lockd(1M)

lockd - network lock daemon SYNOPSIS
/usr/lib/nfs/lockd [-g graceperiod] [-l listen_min_backlog] [-t timeout] [nthreads] DESCRIPTION
The lockd utility is part of the NFS lock manager, which supports record locking operations on NFS files. See fcntl(2) and lockf(3C). The lock manager provides the following two functions: o It forwards fcntl(2) locking requests for NFS mounted file systems to the lock manager on the NFS server. o It generates local file locking operations in response to requests forwarded from lock managers running on NFS client machines. State information kept by the lock manager about these locking requests can be lost if the lockd is killed or the operating system is rebooted. Some of this information can be recovered as follows. When the server lock manager restarts, it waits for a grace period for all client-site lock managers to submit reclaim requests. Client-site lock managers, on the other hand, are notified by the status monitor dae- mon, statd(1M), of the restart and promptly resubmit previously granted lock requests. If the lock daemon fails to secure a previously granted lock at the server site, then it sends SIGLOST to a process. Administrators can make changes to the startup parameters for lockd by logging in as root and editing the /etc/default/nfs file (See nfs(4)). OPTIONS
The following options are supported: -g graceperiod Deprecated in favor of GRACE_PERIOD. Specify the number of seconds that all clients (both NLM and NFSv4) have to reclaim locks after the server reboots. It also controls the NFSv4 lease interval. This option is equivalent to the LOCKD_GRACE_PERIOD parameter. -l listen_min_backlog Specify the listener backlog (listen_min_backlog). listen_min_backlog is the number connect requests that are queued and waiting to be processed before new connect requests start to get dropped. -t timeout Specify the number of seconds to wait before retransmitting a lock request to the remote server. The default value is 15 seconds. Equivalent of the LOCKD_RETRANSMIT_TIMEOUT parameter in the nfs file. OPERANDS
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 of the LOCKD_SERVERS parameter in the nfs file. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWnfscu | +-----------------------------+-----------------------------+ SEE ALSO
svcs(1), automountd(1M), clear_locks(1M), mount_nfs(1M), share(1M), share_nfs(1M), statd(1M), svcadm(1M), fcntl(2), lockf(3C), nfs(4), attributes(5), smf(5) NOTES
The lockd service is managed by the service management facility, smf(5), under the service identifier: svc:/network/nfs/nlockmgr Administrative actions on this service, such as enabling, disabling, or requesting restart, can be performed using svcadm(1M). The ser- vice's status can be queried using the svcs(1) command. If it is disabled, it will be enabled by mount_nfs(1M), share_nfs(1M), and automountd(1M) unless its application/auto_enable prop- erty is set to false. This daemon might not exist in a future release of Solaris. SunOS 5.10 17 Nov 2004 lockd(1M)
Man Page

Featured Tech Videos