1.\" $OpenBSD: rpc.lockd.8,v 1.10 2003/06/12 12:59:53 jmc Exp $ 2.\" 3.\" Copyright (c) 1995 A.R.Gordon, andrew.gordon@net-tel.co.uk 4.\" All rights reserved. 5.\" 6.\" Redistribution and use in source and binary forms, with or without 7.\" modification, are permitted provided that the following conditions 8.\" are met: 9.\" 1. Redistributions of source code must retain the above copyright 10.\" notice, this list of conditions and the following disclaimer. 11.\" 2. Redistributions in binary form must reproduce the above copyright 12.\" notice, this list of conditions and the following disclaimer in the 13.\" documentation and/or other materials provided with the distribution. 14.\" 3. All advertising materials mentioning features or use of this software 15.\" must display the following acknowledgement: 16.\" This product includes software developed by the University of 17.\" California, Berkeley and its contributors. 18.\" 4. Neither the name of the University nor the names of its contributors 19.\" may be used to endorse or promote products derived from this software 20.\" without specific prior written permission. 21.\" 22.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND 23.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE 24.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE 25.\" ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE 26.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL 27.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS 28.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) 29.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT 30.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY 31.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF 32.\" SUCH DAMAGE. 33.\" 34.\" 35.Dd September 24, 1995 36.Dt RPC.LOCKD 8 37.Os 38.Sh NAME 39.Nm rpc.lockd 40.Nd NFS file locking daemon 41.Sh SYNOPSIS 42.Nm rpc.lockd 43.Op Fl d Op Ar debug_level 44.Sh DESCRIPTION 45.Nm rpc.lockd 46is a daemon which provides file- and record-locking services in an NFS 47environment. 48.Pp 49The options are as follows: 50.Bl -tag -width Ds 51.It Fl d Op Ar debug_level 52Write debugging information to syslog, recording 53all RPC transactions to the daemon. 54These messages are logged with level 55.Dv LOG_DEBUG 56and facility 57.Dv LOG_DAEMON . 58If 59.Ar debug_level 60is not specified, 61level 1 is assumed, giving one log line per protocol operation. 62Higher debug levels can be specified, causing display of operation arguments 63and internal operations of the daemon. 64.El 65.Pp 66Error conditions are logged to syslog, irrespective of the debug level, 67using log level 68.Dv LOG_ERR 69and facility 70.Dv LOG_DAEMON . 71.Pp 72The 73.Nm rpc.lockd 74daemon must NOT be invoked by 75.Xr inetd 8 76because the protocol assumes that the daemon will run from system start time. 77Instead, it should be run from 78.Xr rc 8 79after the network has been started. 80.Sh FILES 81.Bl -tag -width /usr/include/rpcsvc/nlm_prot.x -compact 82.It Pa /usr/include/rpcsvc/nlm_prot.x 83RPC protocol specification for the network lock manager protocol. 84.El 85.Sh SEE ALSO 86.Xr syslog 3 , 87.Xr rc 8 88.Sh STANDARDS 89The implementation is based on the specification in X/Open CAE Specification 90C218, "Protocols for X/Open PC Interworking: XNFS, Issue 4", ISBN 1 872630 66 9 91.Sh BUGS 92The current implementation provides only the server side of the protocol 93(i.e., clients running other OS types can establish locks on an 94.Ox 95fileserver, 96but there is currently no means for an 97.Ox 98client to establish locks). 99.Pp 100Versions 1, 2 and 3 of the protocol are supported. 101However, only versions 1022 (Unix systems) and 3 (PC-NFS clients) seem to be in common use - the version 1031 support has not been tested due to the lack of version 1 clients against 104which to test. 105