1 .\" $NetBSD: fcntl.2,v 1.37 2010/05/17 12:16:43 jruoho Exp $
3 .\" Copyright (c) 1983, 1993
4 .\" The Regents of the University of California. All rights reserved.
6 .\" Redistribution and use in source and binary forms, with or without
7 .\" modification, are permitted provided that the following conditions
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. Neither the name of the University nor the names of its contributors
15 .\" may be used to endorse or promote products derived from this software
16 .\" without specific prior written permission.
18 .\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
19 .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
20 .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
21 .\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
22 .\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
23 .\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
24 .\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
25 .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
26 .\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
27 .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
30 .\" @(#)fcntl.2 8.2 (Berkeley) 1/12/94
37 .Nd file descriptor control
43 .Fn fcntl "int fd" "int cmd" "..."
46 provides for control over descriptors.
49 is a descriptor to be operated on by
52 The third parameter is called
54 and is technically a pointer to void, but it is
55 interpreted as an int by some commands and ignored by others.
58 .Bl -tag -width F_GETOWNX
60 Return a new descriptor as follows:
62 .Bl -bullet -compact -offset 4n
64 Lowest numbered available descriptor greater than or equal to
66 which is interpreted as an int.
68 Same object references as the original descriptor.
70 New descriptor shares the same file offset if the object
73 Same access mode (read, write or read/write).
75 Same file status flags (i.e., both file descriptors
76 share the same file status flags).
78 The close-on-exec flag associated with the new file descriptor
79 is cleared to remain open across
84 Get the close-on-exec flag associated with the file descriptor
88 If the returned value ANDed with
91 the file will remain open across
93 otherwise the file will be closed upon execution of
98 Set the close-on-exec flag associated with
108 Get descriptor status flags, as described below
112 Set descriptor status flags to
114 which is interpreted as an int.
116 Get the process ID or process group
121 signals; process groups are returned
126 Set the process or process group
132 process groups are specified by supplying
134 as negative, otherwise
136 is interpreted as a process ID.
139 is interpreted as an int.
141 Close all file descriptors greater than or equal to
144 Return the maximum file descriptor number currently open by the process.
151 flags are as follows:
152 .Bl -tag -width O_NONBLOCKX
154 Non-blocking I/O; if no data is available to a
158 operation would block,
159 the read or write call returns \-1 with the error
162 Force each write to append at the end of file;
170 signal to be sent to the process group
171 when I/O is possible, e.g.,
172 upon availability of data to be read.
175 Several commands are available for doing advisory file locking;
176 they all operate on the following structure:
179 off_t l_start; /* starting offset */
180 off_t l_len; /* len = 0 means until end of file */
181 pid_t l_pid; /* lock owner */
182 short l_type; /* lock type: read/write, etc. */
183 short l_whence; /* type of l_start */
187 The commands available for advisory record locking are as follows:
188 .Bl -tag -width F_SETLKWX
190 Get the first lock that blocks the lock description pointed to by the
193 taken as a pointer to a
196 The information retrieved overwrites the information passed to
201 If no lock is found that would prevent this lock from being created,
202 the structure is left unchanged by this function call except for the
208 Set or clear a file segment lock according to the lock description
209 pointed to by the third argument,
211 taken as a pointer to a
214 As specified by the value of
217 is used to establish shared (or read) locks
219 or exclusive (or write) locks,
221 as well as remove either type of lock
223 If a shared or exclusive lock cannot be set,
225 returns immediately with
228 This command is the same as
230 except that if a shared or exclusive lock is blocked by other locks,
231 the process waits until the request can be satisfied.
232 If a signal that is to be caught is received while
234 is waiting for a region, the
236 will be interrupted if the signal handler has not specified the
242 When a shared lock has been set on a segment of a file,
243 other processes can set shared locks on that segment
245 A shared lock prevents any other process from setting an exclusive
246 lock on any portion of the protected area.
247 A request for a shared lock fails if the file descriptor was not
248 opened with read access.
250 An exclusive lock prevents any other process from setting a shared lock or
251 an exclusive lock on any portion of the protected area.
252 A request for an exclusive lock fails if the file was not
253 opened with write access.
262 to indicate that the relative offset,
264 bytes, will be measured from the start of the file,
265 current position, or end of the file, respectively.
268 is the number of consecutive bytes to be locked.
271 is negative, the result is undefined.
274 field is only used with
276 to return the process ID of the process holding a blocking lock.
279 request, the value of
284 Locks may start and extend beyond the current end of a file,
285 but may not start or extend before the beginning of the file.
286 A lock is set to extend to the largest possible value of the
287 file offset for that file if
294 point to the beginning of the file, and
296 is zero, the entire file is locked.
297 If an application wishes only to do entire file locking, the
299 system call is much more efficient.
301 There is at most one type of lock set for each byte in the file.
302 Before a successful return from an
306 request when the calling process has previously existing locks
307 on bytes in the region specified by the request,
308 the previous lock type for each byte in the specified
309 region is replaced by the new lock type.
310 As specified above under the descriptions
311 of shared locks and exclusive locks, an
315 request fails or blocks respectively when another process has existing
316 locks on bytes in the specified region and the type of any of those
317 locks conflicts with the type specified in the request.
319 This interface follows the completely stupid semantics of
323 that require that all locks associated with a file for a given process are
324 removed when \fIany\fP file descriptor for that file is closed by that process.
325 This semantic means that applications must be aware of any files that
326 a subroutine library may access.
327 For example if an application for updating the password file locks the
328 password file database while making the update, and then calls
330 to retrieve a record,
331 the lock will be lost because
333 opens, reads, and closes the password database.
334 The database close will release all locks that the process has
335 associated with the database, even if the library routine never
336 requested a lock on the database.
338 Another minor semantic problem with this interface is that
339 locks are not inherited by a child process created using the
344 interface has much more rational last close semantics and
345 allows locks to be inherited by child processes.
348 is recommended for applications that want to ensure the integrity
349 of their locks when using library routines or wish to pass locks
355 locks may be safely used concurrently.
357 All locks associated with a file for a given process are
358 removed when the process terminates.
360 A potential for deadlock occurs if a process controlling a locked region
361 is put to sleep by attempting to lock the locked region of another process.
362 This implementation detects that sleeping until a locked region is unlocked
363 would cause a deadlock and fails with an
367 Upon successful completion, the value returned depends on
370 .Bl -tag -width F_GETOWNX -offset indent
372 A new file descriptor.
374 Value of flag (only the low-order bit is defined).
378 Value of file descriptor owner.
380 Value of the highest file descriptor open by the process.
382 Value other than \-1.
385 Otherwise, a value of \-1 is returned and
387 is set to indicate the error.
403 and the segment of a file to be locked is already
404 exclusive-locked by another process;
405 or the type is an exclusive lock and some portion of the
406 segment of a file to be locked is already shared-locked or
407 exclusive-locked by another process.
410 is not a valid open file descriptor.
424 is not a valid file descriptor open for reading.
438 is not a valid file descriptor open for writing.
444 and a deadlock condition was detected.
450 and the function was interrupted by a signal.
462 is negative or greater than the maximum allowable number
464 .Xr getdtablesize 3 ) .
473 and the data to which
475 points is not valid, or
477 refers to a file that does not support locking.
483 and the maximum number of file descriptors permitted for the
484 process are already in use,
485 or no file descriptors greater than or equal to
492 and system-wide the maximum allowed number of file descriptors are
501 and satisfying the lock or unlock request would result in the
502 number of locked regions in the system exceeding a system-imposed limit.
508 the process ID given as argument is not in use.
525 function call appeared in