1 .\" $NetBSD: lockf.3,v 1.2 1998/02/05 18:47:28 perry Exp $
3 .\" Copyright (c) 1997 The NetBSD Foundation, Inc.
4 .\" All rights reserved.
6 .\" This code is derived from software contributed to The NetBSD Foundation
7 .\" by Klaus Klein and S.P. Zeidler.
9 .\" Redistribution and use in source and binary forms, with or without
10 .\" modification, are permitted provided that the following conditions
12 .\" 1. Redistributions of source code must retain the above copyright
13 .\" notice, this list of conditions and the following disclaimer.
14 .\" 2. Redistributions in binary form must reproduce the above copyright
15 .\" notice, this list of conditions and the following disclaimer in the
16 .\" documentation and/or other materials provided with the distribution.
17 .\" 3. All advertising materials mentioning features or use of this software
18 .\" must display the following acknowledgement:
19 .\" This product includes software developed by the NetBSD
20 .\" Foundation, Inc. and its contributors.
21 .\" 4. Neither the name of The NetBSD Foundation nor the names of its
22 .\" contributors may be used to endorse or promote products derived
23 .\" from this software without specific prior written permission.
25 .\" THIS SOFTWARE IS PROVIDED BY THE NETBSD FOUNDATION, INC. AND CONTRIBUTORS
26 .\" ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED
27 .\" TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
28 .\" PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FOUNDATION OR CONTRIBUTORS
29 .\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
30 .\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
31 .\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
32 .\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
33 .\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
34 .\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
35 .\" POSSIBILITY OF SUCH DAMAGE.
37 .\" $FreeBSD: src/lib/libc/gen/lockf.3,v 1.5.2.5 2003/03/13 18:05:37 trhodes Exp $
38 .\" $DragonFly: src/lib/libc/gen/lockf.3,v 1.2 2003/06/17 04:26:42 dillon Exp $
45 .Nd record locking on files
51 .Fn lockf "int filedes" "int function" "off_t size"
55 function allows sections of a file to be locked with advisory-mode locks.
58 from other processes which attempt to lock the locked file section will
59 either return an error value or block until the section becomes unlocked.
60 All the locks for a process are removed when the process terminates.
64 is an open file descriptor.
65 The file descriptor must have been opened either for write-only
73 argument is a control value which specifies the action to be taken.
74 The permissible values for
77 .Bl -tag -width F_ULOCKXX -compact -offset indent
81 unlock locked sections
83 lock a section for exclusive use
85 test and lock a section for exclusive use
87 test a section for locks by other processes
91 removes locks from a section of the file;
95 both lock a section of a file if the section is available;
97 detects if a lock by another process is present on the specified section.
101 argument is the number of contiguous bytes to be locked or
103 The section to be locked or unlocked starts at the current
104 offset in the file and extends forward for a positive size or backward
105 for a negative size (the preceding bytes up to but not including the
106 current offset). However, it is not permitted to lock a section that
107 starts or extends before the beginning of the file.
110 is 0, the section from the current offset through the largest possible
111 file offset is locked (that is, from the current offset through the
112 present or any future end-of-file).
114 The sections locked with
118 may, in whole or in part, contain or be contained by a previously
119 locked section for the same process.
120 When this occurs, or if adjacent
121 locked sections would occur, the sections are combined into a single
123 If the request would cause the number of locks to
124 exceed a system-imposed limit, the request will fail.
129 requests differ only by the action taken if the section is not
132 blocks the calling process until the section is available.
134 makes the function fail if the section is already locked by another
137 File locks are released on first close by the locking process of any
138 file descriptor for the file.
141 requests release (wholly or in part) one or more locked sections
142 controlled by the process.
143 Locked sections will be unlocked starting
144 at the current file offset through
146 bytes or to the end of file if size is 0. When all of a locked section
147 is not released (that is, when the beginning or end of the area to be
148 unlocked falls within a locked section), the remaining portions of
149 that section are still locked by the process.
151 portion of a locked section will cause the remaining locked beginning
152 and end portions to become two separate locked sections.
154 request would cause the number of locks in the system to exceed a
155 system-imposed limit, the request will fail.
159 request in which size is non-zero and the offset of the last byte of
160 the requested section is the maximum value for an object of type
161 off_t, when the process has an existing lock in which size is 0 and
162 which includes the last byte of the requested section, will be treated
163 as a request to unlock from the start of the requested section with a
164 size equal to 0. Otherwise an
166 request will attempt to unlock only the requested section.
168 A potential for deadlock occurs if a process controlling a locked
169 region is put to sleep by attempting to lock the locked region of
170 another process. This implementation detects that sleeping until a
171 locked region is unlocked would cause a deadlock and fails with an
180 locks may be safely used concurrently.
182 Blocking on a section is interrupted by any signal.
185 In the case of a failure, existing locks are not changed.
199 and the section is already locked by another process.
203 is not a valid open file descriptor.
213 is not a valid file descriptor open for writing.
219 and a deadlock is detected.
226 was interrupted by the delivery of a signal.
239 refers to a file that does not support locking.
248 and satisfying the lock or unlock request would result in the number
249 of locked regions in the system exceeding a system-imposed limit.