Man page or keyword search:   man All Sections 1 - General Commands 2 - System Calls 3 - Subroutines, Functions 4 - Special Files 5 - File Formats 6 - Games and Screensavers 7 - Macros and Conventions 8 - Maintenence Commands 9 - Kernel Interface New Commands Server 4.4BSD AIX Alpinelinux Archlinux Aros BSDOS BSDi Bifrost CentOS Cygwin Darwin Debian DigitalUNIX DragonFly ElementaryOS Fedora FreeBSD Gentoo GhostBSD HP-UX Haiku Hurd IRIX Inferno JazzOS Kali Knoppix LinuxMint MacOSX Mageia Mandriva Manjaro Minix MirBSD NeXTSTEP NetBSD OPENSTEP OSF1 OpenBSD OpenDarwin OpenIndiana OpenMandriva OpenServer OpenSuSE OpenVMS Oracle PC-BSD Peanut Pidora Plan9 QNX Raspbian RedHat Scientific Slackware SmartOS Solaris SuSE SunOS Syllable Tru64 UNIXv7 Ubuntu Ultrix UnixWare Xenix YellowDog aLinux   9087 pages apropos Keyword Search (all sections) Output format html ascii pdf view pdf save postscript

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

NAME
     rpc.lockd — NFS file locking daemon

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

DESCRIPTION
     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 sys‐
	     log, recording all RPC transactions to the daemon.	 These mes‐
	     sages 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 display of operation arguments and internal
	     operations of the daemon.

     -g	     The -g option allow to specify the grace period, in seconds. Dur‐
	     ing 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.

FILES
     /usr/include/rpcsvc/nlm_prot.x  RPC protocol specification for the net‐
				     work lock manager protocol.

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

STANDARDS
     The implementation is based on the specification in X/Open CAE Specifica‐
     tion C218, "Protocols for X/Open PC Interworking: XNFS, Issue 4", ISBN 1
     872630 66 9

HISTORY
     A version of rpc.lockd appeared in SunOS 4.

BUGS
     The current implementation provides only the server side of the protocol
     (i.e. clients running other OS types can establish locks on a NetBSD
     fileserver, but there is currently no means for a NetBSD client to estab‐
     lish locks).

     The current implementation serialises locks requests that could be
     shared.

BSD			      September 24, 1995			   BSD

                             _         _         _ 
                            | |       | |       | |     
                            | |       | |       | |     
                         __ | | __ __ | | __ __ | | __  
                         \ \| |/ / \ \| |/ / \ \| |/ /  
                          \ \ / /   \ \ / /   \ \ / /   
                           \   /     \   /     \   /    
                            \_/       \_/       \_/ 

Vote for polarhome