2 .\" Copyright (c) 2011 Apple Inc. All rights reserved.
4 .\" @APPLE_LICENSE_HEADER_START@
6 .\" This file contains Original Code and/or Modifications of Original Code
7 .\" as defined in and that are subject to the Apple Public Source License
8 .\" Version 2.0 (the 'License'). You may not use this file except in
9 .\" compliance with the License. Please obtain a copy of the License at
10 .\" http://www.opensource.apple.com/apsl/ and read it before using this
13 .\" The Original Code and all software distributed under the License are
14 .\" distributed on an 'AS IS' basis, WITHOUT WARRANTY OF ANY KIND, EITHER
15 .\" EXPRESS OR IMPLIED, AND APPLE HEREBY DISCLAIMS ALL SUCH WARRANTIES,
16 .\" INCLUDING WITHOUT LIMITATION, ANY WARRANTIES OF MERCHANTABILITY,
17 .\" FITNESS FOR A PARTICULAR PURPOSE, QUIET ENJOYMENT OR NON-INFRINGEMENT.
18 .\" Please see the License for the specific language governing rights and
19 .\" limitations under the License.
21 .\" @APPLE_LICENSE_HEADER_END@
24 .\" $NetBSD: fcntl.2,v 1.6 1995/02/27 12:32:29 cgd Exp $
26 .\" Copyright (c) 1983, 1993
27 .\" The Regents of the University of California. All rights reserved.
29 .\" Redistribution and use in source and binary forms, with or without
30 .\" modification, are permitted provided that the following conditions
32 .\" 1. Redistributions of source code must retain the above copyright
33 .\" notice, this list of conditions and the following disclaimer.
34 .\" 2. Redistributions in binary form must reproduce the above copyright
35 .\" notice, this list of conditions and the following disclaimer in the
36 .\" documentation and/or other materials provided with the distribution.
37 .\" 3. All advertising materials mentioning features or use of this software
38 .\" must display the following acknowledgement:
39 .\" This product includes software developed by the University of
40 .\" California, Berkeley and its contributors.
41 .\" 4. Neither the name of the University nor the names of its contributors
42 .\" may be used to endorse or promote products derived from this software
43 .\" without specific prior written permission.
45 .\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
46 .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
47 .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
48 .\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
49 .\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
50 .\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
51 .\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
52 .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
53 .\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
54 .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
57 .\" @(#)fcntl.2 8.2 (Berkeley) 1/12/94
66 .Fd #include <fcntl.h>
75 provides for control over descriptors.
78 is a descriptor to be operated on by
81 .Bl -tag -width F_WRITEBOOTSTRAPX
83 Return a new descriptor as follows:
85 .Bl -bullet -compact -offset 4n
87 Lowest numbered available descriptor greater than or equal to
90 Same object references as the original descriptor.
92 New descriptor shares the same file offset if the object
95 Same access mode (read, write or read/write).
97 Same file status flags (i.e., both file descriptors
98 share the same file status flags).
100 The close-on-exec flag associated with the new file descriptor
101 is cleared so that the descriptor remains open across an
105 .It Dv F_DUPFD_CLOEXEC
108 except that the close-on-exec flag associated with the new file descriptor
111 Get the flags associated with the file descriptor
117 Set the file descriptor flags to
120 Get descriptor status flags, as described below
124 Set descriptor status flags to
127 Get the process ID or process group
132 signals; process groups are returned
137 Set the process or process group
143 process groups are specified by supplying
145 as negative, otherwise
147 is interpreted as a process ID.
149 Get the path of the file descriptor
151 The argument must be a buffer of size
155 Preallocate file storage space. Note: upon success,
156 the space that is allocated can be the same size or
157 larger than the space requested.
159 Truncate a file without zeroing space.
160 The calling process must have root privileges.
162 Issue an advisory read async with no copy to user.
164 Turn read ahead off/on.
171 .It Dv F_READBOOTSTRAP
172 Read bootstrap from disk.
173 .It Dv F_WRITEBOOTSTRAP
174 Write bootstrap on disk.
175 The calling process must have root privileges.
177 Turns data caching off/on. A non-zero value in
179 turns data caching off.
182 turns data caching on.
184 Get disk device information.
185 Currently this only includes the
186 disk device address that corresponds
187 to the current file offset.
188 .It Dv F_LOG2PHYS_EXT
189 Variant of F_LOG2PHYS that uses the passed in
190 file offset and length.
192 Does the same thing as
194 then asks the drive to
195 flush all buffered data to
196 the permanent storage device
199 This is currently implemented on HFS, MS-DOS (FAT),
200 and Universal Disk Format (UDF) file systems.
201 The operation may take quite a while to complete.
202 Certain FireWire drives have also been known
203 to ignore the request to flush their buffered data.
204 .It Dv F_SETNOSIGPIPE
207 signal will be generated when a write fails on a pipe or socket for
208 which there is no reader. If
212 generation is disabled for descriptor
216 of zero enables it (the default).
217 .It Dv F_GETNOSIGPIPE
220 signal will be generated when a write fails on a pipe or socket
221 for which there is no reader. The semantics of the return value
232 commands are as follows:
233 .Bl -tag -width FD_CLOEXECX -offset indent
235 Close-on-exec; the given file descriptor will be automatically
236 closed in the successor process image when one of the
240 family of system calls is invoked.
247 commands are as follows:
248 .Bl -tag -width O_NONBLOCKX -offset indent
250 Non-blocking I/O; if no data is available to a
254 operation would block,
255 the read or write call returns -1 with the error
258 Force each write to append at the end of file;
266 signal to be sent to the process group
267 when I/O is possible, e.g.,
268 upon availability of data to be read.
271 Several commands are available for doing advisory file locking;
272 they all operate on the following structure:
276 off_t l_start; /* starting offset */
277 off_t l_len; /* len = 0 means until end of file */
278 pid_t l_pid; /* lock owner */
279 short l_type; /* lock type: read/write, etc. */
280 short l_whence; /* type of l_start */
284 The commands available for advisory record locking are as follows:
285 .Bl -tag -width F_SETLKWX
287 Get the first lock that blocks the lock description pointed to by the
290 taken as a pointer to a
293 The information retrieved overwrites the information passed to
298 If no lock is found that would prevent this lock from being created,
299 the structure is left unchanged by this function call except for the
300 lock type which is set to
303 Set or clear a file segment lock according to the lock description
304 pointed to by the third argument,
306 taken as a pointer to a
310 is used to establish shared (or read) locks
312 or exclusive (or write) locks,
314 as well as remove either type of lock
316 If a shared or exclusive lock cannot be set,
318 returns immediately with
321 This command is the same as
323 except that if a shared or exclusive lock is blocked by other locks,
324 the process waits until the request can be satisfied.
325 If a signal that is to be caught is received while
327 is waiting for a region, the
329 will be interrupted if the signal handler has not specified the
335 When a shared lock has been set on a segment of a file,
336 other processes can set shared locks on that segment
338 A shared lock prevents any other process from setting an exclusive
339 lock on any portion of the protected area.
340 A request for a shared lock fails if the file descriptor was not
341 opened with read access.
343 An exclusive lock prevents any other process from setting a shared lock or
344 an exclusive lock on any portion of the protected area.
345 A request for an exclusive lock fails if the file was not
346 opened with write access.
355 to indicate that the relative offset,
357 bytes, will be measured from the start of the file,
358 current position, or end of the file, respectively.
361 is the number of consecutive bytes to be locked.
364 is negative, the result is undefined.
367 field is only used with
369 to return the process ID of the process holding a blocking lock.
372 request, the value of
377 Locks may start and extend beyond the current end of a file,
378 but may not start or extend before the beginning of the file.
379 A lock is set to extend to the largest possible value of the
380 file offset for that file if
386 point to the beginning of the file, and
388 is zero, the entire file is locked.
389 If an application wishes only to do entire file locking, the
391 system call is much more efficient.
393 There is at most one type of lock set for each byte in the file.
394 Before a successful return from an
398 request when the calling process has previously existing locks
399 on bytes in the region specified by the request,
400 the previous lock type for each byte in the specified
401 region is replaced by the new lock type.
402 As specified above under the descriptions
403 of shared locks and exclusive locks, an
407 request fails or blocks respectively when another process has existing
408 locks on bytes in the specified region and the type of any of those
409 locks conflicts with the type specified in the request.
411 This interface follows the completely stupid semantics of System V and
413 that require that all locks associated with a file for a given process are
414 removed when \fIany\fP file descriptor for that file is closed by that process.
415 This semantic means that applications must be aware of any files that
416 a subroutine library may access.
417 For example if an application for updating the password file locks the
418 password file database while making the update, and then calls
420 to retrieve a record,
421 the lock will be lost because
423 opens, reads, and closes the password database.
424 The database close will release all locks that the process has
425 associated with the database, even if the library routine never
426 requested a lock on the database.
427 Another minor semantic problem with this interface is that
428 locks are not inherited by a child process created using the
433 interface has much more rational last close semantics and
434 allows locks to be inherited by child processes.
436 is recommended for applications that want to ensure the integrity
437 of their locks when using library routines or wish to pass locks
443 locks may be safely used concurrently.
445 All locks associated with a file for a given process are
446 removed when the process terminates.
448 A potential for deadlock occurs if a process controlling a locked region
449 is put to sleep by attempting to lock the locked region of another process.
450 This implementation detects that sleeping until a locked region is unlocked
451 would cause a deadlock and fails with an
457 command operates on the following structure:
460 typedef struct fstore {
461 u_int32_t fst_flags; /* IN: flags word */
462 int fst_posmode; /* IN: indicates offset field */
463 off_t fst_offset; /* IN: start of the region */
464 off_t fst_length; /* IN: size of the region */
465 off_t fst_bytesalloc; /* OUT: number of bytes allocated */
469 The flags (fst_flags) for the
471 command are as follows:
472 .Bl -tag -width F_ALLOCATECONTIGX -offset indent
473 .It Dv F_ALLOCATECONTIG
474 Allocate contiguous space.
476 Allocate all requested space or no space at all.
479 The position modes (fst_posmode) for the
481 command indicate how to use the offset field.
482 The modes are as follows:
483 .Bl -tag -width F_PEOFPOSMODEX -offset indent
485 Allocate from the physical end of file.
487 Allocate from the volume offset.
492 command operates on the following structure
493 which holds information passed from the
498 off_t ra_offset; /* offset into the file */
499 int ra_count; /* size of the read */
504 .Dv F_READBOOTSTRAP and F_WRITEBOOTSTRAP
505 commands operate on the following structure.
508 typedef struct fbootstraptransfer {
509 off_t fbt_offset; /* IN: offset to start read/write */
510 size_t fbt_length; /* IN: number of bytes to transfer */
511 void *fbt_buffer; /* IN: buffer to be read/written */
512 } fbootstraptransfer_t;
517 command operates on the following structure:
521 u_int32_t l2p_flags; /* unused so far */
522 off_t l2p_contigbytes; /* unused so far */
523 off_t l2p_devoffset; /* bytes into device */
529 command operates on the same structure as F_LOG2PHYS but treats it as an in/out:
533 u_int32_t l2p_flags; /* unused so far */
534 off_t l2p_contigbytes; /* IN: number of bytes to be queried;
535 OUT: number of contiguous bytes allocated at this position */
536 off_t l2p_devoffset; /* IN: bytes into file;
537 OUT: bytes into device */
543 is a socket, then the
547 commands are directly analogous, and fully interoperate with the
555 Upon successful completion, the value returned depends on
558 .Bl -tag -width F_GETOWNX -offset indent
560 A new file descriptor.
562 Value of flag (only the low-order bit is defined).
566 Value of file descriptor owner.
571 Otherwise, a value of -1 is returned and
573 is set to indicate the error.
577 system call will fail if:
591 and the segment of a file to be locked is already
592 exclusive-locked by another process;
593 or the type is an exclusive lock and some portion of the
594 segment of a file to be locked is already shared-locked or
595 exclusive-locked by another process.
603 and the calling process does not have root privileges.
607 is not a valid open file descriptor.
621 is not a valid file descriptor open for reading.
635 is not a valid file descriptor open for writing.
641 and the calling process does not have
642 file write permission.
652 is not a valid file descriptor open for reading.
659 and a deadlock condition was detected.
666 and the function was interrupted by a signal.
674 is negative or greater than the maximum allowable number
676 .Xr getdtablesize 2 ) .
685 and the data to which
687 points is not valid, or
689 refers to a file that does not support locking.
707 is a negative or zero value.
715 and the operation was attempted on a non-HFS disk type.
721 and the maximum allowed number of file descriptors are currently
729 and the maximum number of file descriptors permitted for the
730 process are already in use,
731 or no file descriptors greater than or equal to
742 and satisfying the lock or unlock request would result in the
743 number of locked regions in the system exceeding a system-imposed limit.
746 A return value would overflow its representation.
749 is F_GETLK, F_SETLK, or F_SETLKW
750 and the smallest (or, if l_len is non-zero, the largest) offset
751 of a byte in the requested segment
752 will not fit in an object of type off_t.
759 the process ID given as argument is not in use.
765 .Xr getdtablesize 2 ,
774 function call appeared in