it forwards fcntl(2) locking requests for NFS mounted file systems to the lock manager on the NFS server
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 daemon, 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
Specify the number of seconds that clients have to reclaim locks after the server reboots. The default is 45 seconds.
Specify the number of seconds to wait before retransmitting a lock request to the remote server. The default value is 15 seconds.
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.
See attributes(5) for descriptions of the following attributes:
|ATTRIBUTE TYPE||ATTRIBUTE VALUE|
lockd must be started with a UID
of 0, a sensitivity label of
ADMIN_LOW, and a clearance of
ADMIN_HIGH. It must be started from the trusted path and must
have these privileges: