lockd(1M)

NAME | SYNOPSIS | DESCRIPTION | OPTIONS | ATTRIBUTES | SUMMARY OF TRUSTED SOLARIS CHANGES | SEE ALSO

NAME

lockd– Network lock daemon

SYNOPSIS

/usr/lib/nfs/lockd [-g graceperiod] [-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 two functions:

• 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 SIGLOST to a process.

OPTIONS

-g graceperiod

Specify the number of seconds that clients have to reclaim locks after the server reboots. The default is 45 seconds.

-t timeout

Specify the number of seconds to wait before retransmitting a lock request to the remote server. The default value is 15 seconds.

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.

ATTRIBUTES

See attributes(5) for descriptions of the following attributes:

ATTRIBUTE TYPE	ATTRIBUTE VALUE
Availability	SUNWcsu

SUMMARY OF TRUSTED SOLARIS CHANGES

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: net_mac_read, net_privaddr, net_upgrade_sl, and sys_nfs.

SEE ALSO

Trusted Solaris 8 HW 12/02 Reference Manual

statd(1M), fcntl(2)

SunOS 5.8 Reference Manual

lockf(3C), attributes(5)

NAME | SYNOPSIS | DESCRIPTION | OPTIONS | ATTRIBUTES | SUMMARY OF TRUSTED SOLARIS CHANGES | SEE ALSO