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. Note that if the
188 file offset is not backed by physical blocks
189 we can return -1 as the offset. This is subject
191 .It Dv F_LOG2PHYS_EXT
192 Variant of F_LOG2PHYS that uses the passed in
193 file offset and length.
195 Does the same thing as
197 then asks the drive to
198 flush all buffered data to
199 the permanent storage device
202 This is currently implemented on HFS, MS-DOS (FAT),
203 and Universal Disk Format (UDF) file systems.
204 The operation may take quite a while to complete.
205 Certain FireWire drives have also been known
206 to ignore the request to flush their buffered data.
207 .It Dv F_SETNOSIGPIPE
210 signal will be generated when a write fails on a pipe or socket for
211 which there is no reader. If
215 generation is disabled for descriptor
219 of zero enables it (the default).
220 .It Dv F_GETNOSIGPIPE
223 signal will be generated when a write fails on a pipe or socket
224 for which there is no reader. The semantics of the return value
235 commands are as follows:
236 .Bl -tag -width FD_CLOEXECX -offset indent
238 Close-on-exec; the given file descriptor will be automatically
239 closed in the successor process image when one of the
243 family of system calls is invoked.
250 commands are as follows:
251 .Bl -tag -width O_NONBLOCKX -offset indent
253 Non-blocking I/O; if no data is available to a
257 operation would block,
258 the read or write call returns -1 with the error
261 Force each write to append at the end of file;
269 signal to be sent to the process group
270 when I/O is possible, e.g.,
271 upon availability of data to be read.
274 Several commands are available for doing advisory file locking;
275 they all operate on the following structure:
279 off_t l_start; /* starting offset */
280 off_t l_len; /* len = 0 means until end of file */
281 pid_t l_pid; /* lock owner */
282 short l_type; /* lock type: read/write, etc. */
283 short l_whence; /* type of l_start */
287 The commands available for advisory record locking are as follows:
288 .Bl -tag -width F_SETLKWX
290 Get the first lock that blocks the lock description pointed to by the
293 taken as a pointer to a
296 The information retrieved overwrites the information passed to
301 If no lock is found that would prevent this lock from being created,
302 the structure is left unchanged by this function call except for the
303 lock type which is set to
306 Set or clear a file segment lock according to the lock description
307 pointed to by the third argument,
309 taken as a pointer to a
313 is used to establish shared (or read) locks
315 or exclusive (or write) locks,
317 as well as remove either type of lock
319 If a shared or exclusive lock cannot be set,
321 returns immediately with
324 This command is the same as
326 except that if a shared or exclusive lock is blocked by other locks,
327 the process waits until the request can be satisfied.
328 If a signal that is to be caught is received while
330 is waiting for a region, the
332 will be interrupted if the signal handler has not specified the
338 When a shared lock has been set on a segment of a file,
339 other processes can set shared locks on that segment
341 A shared lock prevents any other process from setting an exclusive
342 lock on any portion of the protected area.
343 A request for a shared lock fails if the file descriptor was not
344 opened with read access.
346 An exclusive lock prevents any other process from setting a shared lock or
347 an exclusive lock on any portion of the protected area.
348 A request for an exclusive lock fails if the file was not
349 opened with write access.
358 to indicate that the relative offset,
360 bytes, will be measured from the start of the file,
361 current position, or end of the file, respectively.
364 is the number of consecutive bytes to be locked.
367 is negative, the result is undefined.
370 field is only used with
372 to return the process ID of the process holding a blocking lock.
375 request, the value of
380 Locks may start and extend beyond the current end of a file,
381 but may not start or extend before the beginning of the file.
382 A lock is set to extend to the largest possible value of the
383 file offset for that file if
389 point to the beginning of the file, and
391 is zero, the entire file is locked.
392 If an application wishes only to do entire file locking, the
394 system call is much more efficient.
396 There is at most one type of lock set for each byte in the file.
397 Before a successful return from an
401 request when the calling process has previously existing locks
402 on bytes in the region specified by the request,
403 the previous lock type for each byte in the specified
404 region is replaced by the new lock type.
405 As specified above under the descriptions
406 of shared locks and exclusive locks, an
410 request fails or blocks respectively when another process has existing
411 locks on bytes in the specified region and the type of any of those
412 locks conflicts with the type specified in the request.
414 This interface follows the completely stupid semantics of System V and
416 that require that all locks associated with a file for a given process are
417 removed when \fIany\fP file descriptor for that file is closed by that process.
418 This semantic means that applications must be aware of any files that
419 a subroutine library may access.
420 For example if an application for updating the password file locks the
421 password file database while making the update, and then calls
423 to retrieve a record,
424 the lock will be lost because
426 opens, reads, and closes the password database.
427 The database close will release all locks that the process has
428 associated with the database, even if the library routine never
429 requested a lock on the database.
430 Another minor semantic problem with this interface is that
431 locks are not inherited by a child process created using the
436 interface has much more rational last close semantics and
437 allows locks to be inherited by child processes.
439 is recommended for applications that want to ensure the integrity
440 of their locks when using library routines or wish to pass locks
446 locks may be safely used concurrently.
448 All locks associated with a file for a given process are
449 removed when the process terminates.
451 A potential for deadlock occurs if a process controlling a locked region
452 is put to sleep by attempting to lock the locked region of another process.
453 This implementation detects that sleeping until a locked region is unlocked
454 would cause a deadlock and fails with an
460 command operates on the following structure:
463 typedef struct fstore {
464 u_int32_t fst_flags; /* IN: flags word */
465 int fst_posmode; /* IN: indicates offset field */
466 off_t fst_offset; /* IN: start of the region */
467 off_t fst_length; /* IN: size of the region */
468 off_t fst_bytesalloc; /* OUT: number of bytes allocated */
472 The flags (fst_flags) for the
474 command are as follows:
475 .Bl -tag -width F_ALLOCATECONTIGX -offset indent
476 .It Dv F_ALLOCATECONTIG
477 Allocate contiguous space.
479 Allocate all requested space or no space at all.
482 The position modes (fst_posmode) for the
484 command indicate how to use the offset field.
485 The modes are as follows:
486 .Bl -tag -width F_PEOFPOSMODEX -offset indent
488 Allocate from the physical end of file.
490 Allocate from the volume offset.
495 command operates on the following structure
496 which holds information passed from the
501 off_t ra_offset; /* offset into the file */
502 int ra_count; /* size of the read */
507 .Dv F_READBOOTSTRAP and F_WRITEBOOTSTRAP
508 commands operate on the following structure.
511 typedef struct fbootstraptransfer {
512 off_t fbt_offset; /* IN: offset to start read/write */
513 size_t fbt_length; /* IN: number of bytes to transfer */
514 void *fbt_buffer; /* IN: buffer to be read/written */
515 } fbootstraptransfer_t;
520 command operates on the following structure:
524 u_int32_t l2p_flags; /* unused so far */
525 off_t l2p_contigbytes; /* unused so far */
526 off_t l2p_devoffset; /* bytes into device */
532 command operates on the same structure as F_LOG2PHYS but treats it as an in/out:
536 u_int32_t l2p_flags; /* unused so far */
537 off_t l2p_contigbytes; /* IN: number of bytes to be queried;
538 OUT: number of contiguous bytes allocated at this position */
539 off_t l2p_devoffset; /* IN: bytes into file;
540 OUT: bytes into device */
546 is a socket, then the
550 commands are directly analogous, and fully interoperate with the
558 Upon successful completion, the value returned depends on
561 .Bl -tag -width F_GETOWNX -offset indent
563 A new file descriptor.
565 Value of flag (only the low-order bit is defined).
569 Value of file descriptor owner.
574 Otherwise, a value of -1 is returned and
576 is set to indicate the error.
580 system call will fail if:
594 and the segment of a file to be locked is already
595 exclusive-locked by another process;
596 or the type is an exclusive lock and some portion of the
597 segment of a file to be locked is already shared-locked or
598 exclusive-locked by another process.
606 and the calling process does not have root privileges.
610 is not a valid open file descriptor.
624 is not a valid file descriptor open for reading.
638 is not a valid file descriptor open for writing.
644 and the calling process does not have
645 file write permission.
655 is not a valid file descriptor open for reading.
662 and a deadlock condition was detected.
669 and the function was interrupted by a signal.
677 is negative or greater than the maximum allowable number
679 .Xr getdtablesize 2 ) .
688 and the data to which
690 points is not valid, or
692 refers to a file that does not support locking.
710 is a negative or zero value.
718 and the operation was attempted on a non-HFS disk type.
724 and the maximum allowed number of file descriptors are currently
732 and the maximum number of file descriptors permitted for the
733 process are already in use,
734 or no file descriptors greater than or equal to
745 and satisfying the lock or unlock request would result in the
746 number of locked regions in the system exceeding a system-imposed limit.
749 A return value would overflow its representation.
752 is F_GETLK, F_SETLK, or F_SETLKW
753 and the smallest (or, if l_len is non-zero, the largest) offset
754 of a byte in the requested segment
755 will not fit in an object of type off_t.
762 the process ID given as argument is not in use.
768 .Xr getdtablesize 2 ,
777 function call appeared in