]>
Commit | Line | Data |
---|---|---|
28f540f4 | 1 | @node Low-Level I/O, File System Interface, I/O on Streams, Top |
7a68c94a | 2 | @c %MENU% Low-level, less portable I/O |
28f540f4 RM |
3 | @chapter Low-Level Input/Output |
4 | ||
5 | This chapter describes functions for performing low-level input/output | |
6 | operations on file descriptors. These functions include the primitives | |
7 | for the higher-level I/O functions described in @ref{I/O on Streams}, as | |
8 | well as functions for performing low-level control operations for which | |
9 | there are no equivalents on streams. | |
10 | ||
11 | Stream-level I/O is more flexible and usually more convenient; | |
12 | therefore, programmers generally use the descriptor-level functions only | |
13 | when necessary. These are some of the usual reasons: | |
14 | ||
15 | @itemize @bullet | |
16 | @item | |
17 | For reading binary files in large chunks. | |
18 | ||
19 | @item | |
20 | For reading an entire file into core before parsing it. | |
21 | ||
22 | @item | |
23 | To perform operations other than data transfer, which can only be done | |
24 | with a descriptor. (You can use @code{fileno} to get the descriptor | |
25 | corresponding to a stream.) | |
26 | ||
27 | @item | |
28 | To pass descriptors to a child process. (The child can create its own | |
29 | stream to use a descriptor that it inherits, but cannot inherit a stream | |
30 | directly.) | |
31 | @end itemize | |
32 | ||
33 | @menu | |
34 | * Opening and Closing Files:: How to open and close file | |
2c6fe0bd | 35 | descriptors. |
28f540f4 RM |
36 | * I/O Primitives:: Reading and writing data. |
37 | * File Position Primitive:: Setting a descriptor's file | |
2c6fe0bd | 38 | position. |
28f540f4 RM |
39 | * Descriptors and Streams:: Converting descriptor to stream |
40 | or vice-versa. | |
41 | * Stream/Descriptor Precautions:: Precautions needed if you use both | |
42 | descriptors and streams. | |
49c091e5 | 43 | * Scatter-Gather:: Fast I/O to discontinuous buffers. |
07435eb4 | 44 | * Memory-mapped I/O:: Using files like memory. |
28f540f4 RM |
45 | * Waiting for I/O:: How to check for input or output |
46 | on multiple file descriptors. | |
dfd2257a | 47 | * Synchronizing I/O:: Making sure all I/O actions completed. |
b07d03e0 | 48 | * Asynchronous I/O:: Perform I/O in parallel. |
28f540f4 RM |
49 | * Control Operations:: Various other operations on file |
50 | descriptors. | |
51 | * Duplicating Descriptors:: Fcntl commands for duplicating | |
52 | file descriptors. | |
53 | * Descriptor Flags:: Fcntl commands for manipulating | |
54 | flags associated with file | |
2c6fe0bd | 55 | descriptors. |
28f540f4 RM |
56 | * File Status Flags:: Fcntl commands for manipulating |
57 | flags associated with open files. | |
58 | * File Locks:: Fcntl commands for implementing | |
59 | file locking. | |
60 | * Interrupt Input:: Getting an asynchronous signal when | |
61 | input arrives. | |
07435eb4 | 62 | * IOCTLs:: Generic I/O Control operations. |
28f540f4 RM |
63 | @end menu |
64 | ||
65 | ||
66 | @node Opening and Closing Files | |
67 | @section Opening and Closing Files | |
68 | ||
69 | @cindex opening a file descriptor | |
70 | @cindex closing a file descriptor | |
71 | This section describes the primitives for opening and closing files | |
72 | using file descriptors. The @code{open} and @code{creat} functions are | |
73 | declared in the header file @file{fcntl.h}, while @code{close} is | |
74 | declared in @file{unistd.h}. | |
75 | @pindex unistd.h | |
76 | @pindex fcntl.h | |
77 | ||
78 | @comment fcntl.h | |
79 | @comment POSIX.1 | |
80 | @deftypefun int open (const char *@var{filename}, int @var{flags}[, mode_t @var{mode}]) | |
624254b1 SC |
81 | The @code{open} function creates and returns a new file descriptor for |
82 | the file named by @var{filename}. Initially, the file position | |
28f540f4 | 83 | indicator for the file is at the beginning of the file. The argument |
624254b1 SC |
84 | @var{mode} (@pxref{Permission Bits}) is used only when a file is |
85 | created, but it doesn't hurt to supply the argument in any case. | |
28f540f4 RM |
86 | |
87 | The @var{flags} argument controls how the file is to be opened. This is | |
88 | a bit mask; you create the value by the bitwise OR of the appropriate | |
89 | parameters (using the @samp{|} operator in C). | |
90 | @xref{File Status Flags}, for the parameters available. | |
91 | ||
92 | The normal return value from @code{open} is a non-negative integer file | |
07435eb4 | 93 | descriptor. In the case of an error, a value of @math{-1} is returned |
28f540f4 RM |
94 | instead. In addition to the usual file name errors (@pxref{File |
95 | Name Errors}), the following @code{errno} error conditions are defined | |
96 | for this function: | |
97 | ||
98 | @table @code | |
99 | @item EACCES | |
19e4c7dd AJ |
100 | The file exists but is not readable/writable as requested by the @var{flags} |
101 | argument, the file does not exist and the directory is unwritable so | |
28f540f4 RM |
102 | it cannot be created. |
103 | ||
104 | @item EEXIST | |
105 | Both @code{O_CREAT} and @code{O_EXCL} are set, and the named file already | |
106 | exists. | |
107 | ||
108 | @item EINTR | |
109 | The @code{open} operation was interrupted by a signal. | |
110 | @xref{Interrupted Primitives}. | |
111 | ||
112 | @item EISDIR | |
113 | The @var{flags} argument specified write access, and the file is a directory. | |
114 | ||
115 | @item EMFILE | |
116 | The process has too many files open. | |
117 | The maximum number of file descriptors is controlled by the | |
118 | @code{RLIMIT_NOFILE} resource limit; @pxref{Limits on Resources}. | |
119 | ||
120 | @item ENFILE | |
121 | The entire system, or perhaps the file system which contains the | |
122 | directory, cannot support any additional open files at the moment. | |
a7a93d50 | 123 | (This problem cannot happen on @gnuhurdsystems{}.) |
28f540f4 RM |
124 | |
125 | @item ENOENT | |
126 | The named file does not exist, and @code{O_CREAT} is not specified. | |
127 | ||
128 | @item ENOSPC | |
129 | The directory or file system that would contain the new file cannot be | |
130 | extended, because there is no disk space left. | |
131 | ||
132 | @item ENXIO | |
133 | @code{O_NONBLOCK} and @code{O_WRONLY} are both set in the @var{flags} | |
134 | argument, the file named by @var{filename} is a FIFO (@pxref{Pipes and | |
135 | FIFOs}), and no process has the file open for reading. | |
136 | ||
137 | @item EROFS | |
138 | The file resides on a read-only file system and any of @w{@code{O_WRONLY}}, | |
139 | @code{O_RDWR}, and @code{O_TRUNC} are set in the @var{flags} argument, | |
140 | or @code{O_CREAT} is set and the file does not already exist. | |
141 | @end table | |
142 | ||
143 | @c !!! umask | |
144 | ||
04b9968b | 145 | If on a 32 bit machine the sources are translated with |
b07d03e0 UD |
146 | @code{_FILE_OFFSET_BITS == 64} the function @code{open} returns a file |
147 | descriptor opened in the large file mode which enables the file handling | |
fed8f7f7 | 148 | functions to use files up to @math{2^63} bytes in size and offset from |
b07d03e0 UD |
149 | @math{-2^63} to @math{2^63}. This happens transparently for the user |
150 | since all of the lowlevel file handling functions are equally replaced. | |
151 | ||
04b9968b | 152 | This function is a cancellation point in multi-threaded programs. This |
dfd2257a UD |
153 | is a problem if the thread allocates some resources (like memory, file |
154 | descriptors, semaphores or whatever) at the time @code{open} is | |
19e4c7dd | 155 | called. If the thread gets canceled these resources stay allocated |
dfd2257a | 156 | until the program ends. To avoid this calls to @code{open} should be |
04b9968b | 157 | protected using cancellation handlers. |
dfd2257a UD |
158 | @c ref pthread_cleanup_push / pthread_cleanup_pop |
159 | ||
28f540f4 RM |
160 | The @code{open} function is the underlying primitive for the @code{fopen} |
161 | and @code{freopen} functions, that create streams. | |
162 | @end deftypefun | |
163 | ||
b07d03e0 | 164 | @comment fcntl.h |
a3a4a74e | 165 | @comment Unix98 |
b07d03e0 UD |
166 | @deftypefun int open64 (const char *@var{filename}, int @var{flags}[, mode_t @var{mode}]) |
167 | This function is similar to @code{open}. It returns a file descriptor | |
168 | which can be used to access the file named by @var{filename}. The only | |
04b9968b | 169 | difference is that on 32 bit systems the file is opened in the |
b07d03e0 UD |
170 | large file mode. I.e., file length and file offsets can exceed 31 bits. |
171 | ||
b07d03e0 UD |
172 | When the sources are translated with @code{_FILE_OFFSET_BITS == 64} this |
173 | function is actually available under the name @code{open}. I.e., the | |
174 | new, extended API using 64 bit file sizes and offsets transparently | |
175 | replaces the old API. | |
176 | @end deftypefun | |
177 | ||
28f540f4 RM |
178 | @comment fcntl.h |
179 | @comment POSIX.1 | |
180 | @deftypefn {Obsolete function} int creat (const char *@var{filename}, mode_t @var{mode}) | |
181 | This function is obsolete. The call: | |
182 | ||
183 | @smallexample | |
184 | creat (@var{filename}, @var{mode}) | |
185 | @end smallexample | |
186 | ||
187 | @noindent | |
188 | is equivalent to: | |
189 | ||
190 | @smallexample | |
191 | open (@var{filename}, O_WRONLY | O_CREAT | O_TRUNC, @var{mode}) | |
192 | @end smallexample | |
b07d03e0 | 193 | |
04b9968b | 194 | If on a 32 bit machine the sources are translated with |
b07d03e0 UD |
195 | @code{_FILE_OFFSET_BITS == 64} the function @code{creat} returns a file |
196 | descriptor opened in the large file mode which enables the file handling | |
197 | functions to use files up to @math{2^63} in size and offset from | |
198 | @math{-2^63} to @math{2^63}. This happens transparently for the user | |
199 | since all of the lowlevel file handling functions are equally replaced. | |
200 | @end deftypefn | |
201 | ||
202 | @comment fcntl.h | |
a3a4a74e | 203 | @comment Unix98 |
b07d03e0 UD |
204 | @deftypefn {Obsolete function} int creat64 (const char *@var{filename}, mode_t @var{mode}) |
205 | This function is similar to @code{creat}. It returns a file descriptor | |
206 | which can be used to access the file named by @var{filename}. The only | |
04b9968b | 207 | the difference is that on 32 bit systems the file is opened in the |
b07d03e0 UD |
208 | large file mode. I.e., file length and file offsets can exceed 31 bits. |
209 | ||
210 | To use this file descriptor one must not use the normal operations but | |
211 | instead the counterparts named @code{*64}, e.g., @code{read64}. | |
212 | ||
213 | When the sources are translated with @code{_FILE_OFFSET_BITS == 64} this | |
214 | function is actually available under the name @code{open}. I.e., the | |
215 | new, extended API using 64 bit file sizes and offsets transparently | |
216 | replaces the old API. | |
28f540f4 RM |
217 | @end deftypefn |
218 | ||
219 | @comment unistd.h | |
220 | @comment POSIX.1 | |
221 | @deftypefun int close (int @var{filedes}) | |
222 | The function @code{close} closes the file descriptor @var{filedes}. | |
223 | Closing a file has the following consequences: | |
224 | ||
225 | @itemize @bullet | |
2c6fe0bd | 226 | @item |
28f540f4 RM |
227 | The file descriptor is deallocated. |
228 | ||
229 | @item | |
230 | Any record locks owned by the process on the file are unlocked. | |
231 | ||
232 | @item | |
233 | When all file descriptors associated with a pipe or FIFO have been closed, | |
234 | any unread data is discarded. | |
235 | @end itemize | |
236 | ||
04b9968b | 237 | This function is a cancellation point in multi-threaded programs. This |
dfd2257a UD |
238 | is a problem if the thread allocates some resources (like memory, file |
239 | descriptors, semaphores or whatever) at the time @code{close} is | |
19e4c7dd | 240 | called. If the thread gets canceled these resources stay allocated |
04b9968b UD |
241 | until the program ends. To avoid this, calls to @code{close} should be |
242 | protected using cancellation handlers. | |
dfd2257a UD |
243 | @c ref pthread_cleanup_push / pthread_cleanup_pop |
244 | ||
07435eb4 | 245 | The normal return value from @code{close} is @math{0}; a value of @math{-1} |
28f540f4 RM |
246 | is returned in case of failure. The following @code{errno} error |
247 | conditions are defined for this function: | |
248 | ||
249 | @table @code | |
250 | @item EBADF | |
251 | The @var{filedes} argument is not a valid file descriptor. | |
252 | ||
253 | @item EINTR | |
254 | The @code{close} call was interrupted by a signal. | |
255 | @xref{Interrupted Primitives}. | |
256 | Here is an example of how to handle @code{EINTR} properly: | |
257 | ||
258 | @smallexample | |
259 | TEMP_FAILURE_RETRY (close (desc)); | |
260 | @end smallexample | |
261 | ||
262 | @item ENOSPC | |
263 | @itemx EIO | |
264 | @itemx EDQUOT | |
2c6fe0bd | 265 | When the file is accessed by NFS, these errors from @code{write} can sometimes |
28f540f4 RM |
266 | not be detected until @code{close}. @xref{I/O Primitives}, for details |
267 | on their meaning. | |
268 | @end table | |
b07d03e0 UD |
269 | |
270 | Please note that there is @emph{no} separate @code{close64} function. | |
271 | This is not necessary since this function does not determine nor depend | |
fed8f7f7 | 272 | on the mode of the file. The kernel which performs the @code{close} |
04b9968b | 273 | operation knows which mode the descriptor is used for and can handle |
b07d03e0 | 274 | this situation. |
28f540f4 RM |
275 | @end deftypefun |
276 | ||
277 | To close a stream, call @code{fclose} (@pxref{Closing Streams}) instead | |
278 | of trying to close its underlying file descriptor with @code{close}. | |
279 | This flushes any buffered output and updates the stream object to | |
280 | indicate that it is closed. | |
281 | ||
282 | @node I/O Primitives | |
283 | @section Input and Output Primitives | |
284 | ||
285 | This section describes the functions for performing primitive input and | |
286 | output operations on file descriptors: @code{read}, @code{write}, and | |
287 | @code{lseek}. These functions are declared in the header file | |
288 | @file{unistd.h}. | |
289 | @pindex unistd.h | |
290 | ||
291 | @comment unistd.h | |
292 | @comment POSIX.1 | |
293 | @deftp {Data Type} ssize_t | |
294 | This data type is used to represent the sizes of blocks that can be | |
295 | read or written in a single operation. It is similar to @code{size_t}, | |
296 | but must be a signed type. | |
297 | @end deftp | |
298 | ||
299 | @cindex reading from a file descriptor | |
300 | @comment unistd.h | |
301 | @comment POSIX.1 | |
302 | @deftypefun ssize_t read (int @var{filedes}, void *@var{buffer}, size_t @var{size}) | |
303 | The @code{read} function reads up to @var{size} bytes from the file | |
304 | with descriptor @var{filedes}, storing the results in the @var{buffer}. | |
04b9968b UD |
305 | (This is not necessarily a character string, and no terminating null |
306 | character is added.) | |
28f540f4 RM |
307 | |
308 | @cindex end-of-file, on a file descriptor | |
309 | The return value is the number of bytes actually read. This might be | |
310 | less than @var{size}; for example, if there aren't that many bytes left | |
311 | in the file or if there aren't that many bytes immediately available. | |
312 | The exact behavior depends on what kind of file it is. Note that | |
313 | reading less than @var{size} bytes is not an error. | |
314 | ||
315 | A value of zero indicates end-of-file (except if the value of the | |
316 | @var{size} argument is also zero). This is not considered an error. | |
317 | If you keep calling @code{read} while at end-of-file, it will keep | |
318 | returning zero and doing nothing else. | |
319 | ||
320 | If @code{read} returns at least one character, there is no way you can | |
321 | tell whether end-of-file was reached. But if you did reach the end, the | |
322 | next read will return zero. | |
323 | ||
07435eb4 | 324 | In case of an error, @code{read} returns @math{-1}. The following |
28f540f4 RM |
325 | @code{errno} error conditions are defined for this function: |
326 | ||
327 | @table @code | |
328 | @item EAGAIN | |
329 | Normally, when no input is immediately available, @code{read} waits for | |
330 | some input. But if the @code{O_NONBLOCK} flag is set for the file | |
331 | (@pxref{File Status Flags}), @code{read} returns immediately without | |
332 | reading any data, and reports this error. | |
333 | ||
334 | @strong{Compatibility Note:} Most versions of BSD Unix use a different | |
1f77f049 | 335 | error code for this: @code{EWOULDBLOCK}. In @theglibc{}, |
28f540f4 RM |
336 | @code{EWOULDBLOCK} is an alias for @code{EAGAIN}, so it doesn't matter |
337 | which name you use. | |
338 | ||
339 | On some systems, reading a large amount of data from a character special | |
340 | file can also fail with @code{EAGAIN} if the kernel cannot find enough | |
341 | physical memory to lock down the user's pages. This is limited to | |
342 | devices that transfer with direct memory access into the user's memory, | |
343 | which means it does not include terminals, since they always use | |
a7a93d50 JM |
344 | separate buffers inside the kernel. This problem never happens on |
345 | @gnuhurdsystems{}. | |
28f540f4 RM |
346 | |
347 | Any condition that could result in @code{EAGAIN} can instead result in a | |
348 | successful @code{read} which returns fewer bytes than requested. | |
349 | Calling @code{read} again immediately would result in @code{EAGAIN}. | |
350 | ||
351 | @item EBADF | |
352 | The @var{filedes} argument is not a valid file descriptor, | |
353 | or is not open for reading. | |
354 | ||
355 | @item EINTR | |
356 | @code{read} was interrupted by a signal while it was waiting for input. | |
357 | @xref{Interrupted Primitives}. A signal will not necessary cause | |
358 | @code{read} to return @code{EINTR}; it may instead result in a | |
359 | successful @code{read} which returns fewer bytes than requested. | |
360 | ||
361 | @item EIO | |
362 | For many devices, and for disk files, this error code indicates | |
363 | a hardware error. | |
364 | ||
365 | @code{EIO} also occurs when a background process tries to read from the | |
366 | controlling terminal, and the normal action of stopping the process by | |
367 | sending it a @code{SIGTTIN} signal isn't working. This might happen if | |
04b9968b | 368 | the signal is being blocked or ignored, or because the process group is |
28f540f4 RM |
369 | orphaned. @xref{Job Control}, for more information about job control, |
370 | and @ref{Signal Handling}, for information about signals. | |
7e583a52 RM |
371 | |
372 | @item EINVAL | |
373 | In some systems, when reading from a character or block device, position | |
374 | and size offsets must be aligned to a particular block size. This error | |
375 | indicates that the offsets were not properly aligned. | |
28f540f4 RM |
376 | @end table |
377 | ||
b07d03e0 UD |
378 | Please note that there is no function named @code{read64}. This is not |
379 | necessary since this function does not directly modify or handle the | |
380 | possibly wide file offset. Since the kernel handles this state | |
04b9968b | 381 | internally, the @code{read} function can be used for all cases. |
b07d03e0 | 382 | |
04b9968b | 383 | This function is a cancellation point in multi-threaded programs. This |
dfd2257a UD |
384 | is a problem if the thread allocates some resources (like memory, file |
385 | descriptors, semaphores or whatever) at the time @code{read} is | |
19e4c7dd | 386 | called. If the thread gets canceled these resources stay allocated |
04b9968b UD |
387 | until the program ends. To avoid this, calls to @code{read} should be |
388 | protected using cancellation handlers. | |
dfd2257a UD |
389 | @c ref pthread_cleanup_push / pthread_cleanup_pop |
390 | ||
28f540f4 RM |
391 | The @code{read} function is the underlying primitive for all of the |
392 | functions that read from streams, such as @code{fgetc}. | |
393 | @end deftypefun | |
394 | ||
a5a0310d UD |
395 | @comment unistd.h |
396 | @comment Unix98 | |
397 | @deftypefun ssize_t pread (int @var{filedes}, void *@var{buffer}, size_t @var{size}, off_t @var{offset}) | |
398 | The @code{pread} function is similar to the @code{read} function. The | |
04b9968b UD |
399 | first three arguments are identical, and the return values and error |
400 | codes also correspond. | |
a5a0310d UD |
401 | |
402 | The difference is the fourth argument and its handling. The data block | |
403 | is not read from the current position of the file descriptor | |
404 | @code{filedes}. Instead the data is read from the file starting at | |
405 | position @var{offset}. The position of the file descriptor itself is | |
04b9968b | 406 | not affected by the operation. The value is the same as before the call. |
a5a0310d | 407 | |
b07d03e0 UD |
408 | When the source file is compiled with @code{_FILE_OFFSET_BITS == 64} the |
409 | @code{pread} function is in fact @code{pread64} and the type | |
04b9968b | 410 | @code{off_t} has 64 bits, which makes it possible to handle files up to |
c756c71c | 411 | @math{2^63} bytes in length. |
b07d03e0 | 412 | |
a5a0310d UD |
413 | The return value of @code{pread} describes the number of bytes read. |
414 | In the error case it returns @math{-1} like @code{read} does and the | |
04b9968b UD |
415 | error codes are also the same, with these additions: |
416 | ||
a5a0310d UD |
417 | @table @code |
418 | @item EINVAL | |
419 | The value given for @var{offset} is negative and therefore illegal. | |
420 | ||
421 | @item ESPIPE | |
422 | The file descriptor @var{filedes} is associate with a pipe or a FIFO and | |
423 | this device does not allow positioning of the file pointer. | |
424 | @end table | |
425 | ||
426 | The function is an extension defined in the Unix Single Specification | |
427 | version 2. | |
428 | @end deftypefun | |
429 | ||
b07d03e0 | 430 | @comment unistd.h |
a3a4a74e | 431 | @comment Unix98 |
b07d03e0 UD |
432 | @deftypefun ssize_t pread64 (int @var{filedes}, void *@var{buffer}, size_t @var{size}, off64_t @var{offset}) |
433 | This function is similar to the @code{pread} function. The difference | |
434 | is that the @var{offset} parameter is of type @code{off64_t} instead of | |
04b9968b | 435 | @code{off_t} which makes it possible on 32 bit machines to address |
c756c71c | 436 | files larger than @math{2^31} bytes and up to @math{2^63} bytes. The |
b07d03e0 UD |
437 | file descriptor @code{filedes} must be opened using @code{open64} since |
438 | otherwise the large offsets possible with @code{off64_t} will lead to | |
439 | errors with a descriptor in small file mode. | |
440 | ||
c756c71c | 441 | When the source file is compiled with @code{_FILE_OFFSET_BITS == 64} on a |
04b9968b UD |
442 | 32 bit machine this function is actually available under the name |
443 | @code{pread} and so transparently replaces the 32 bit interface. | |
b07d03e0 UD |
444 | @end deftypefun |
445 | ||
28f540f4 RM |
446 | @cindex writing to a file descriptor |
447 | @comment unistd.h | |
448 | @comment POSIX.1 | |
449 | @deftypefun ssize_t write (int @var{filedes}, const void *@var{buffer}, size_t @var{size}) | |
450 | The @code{write} function writes up to @var{size} bytes from | |
451 | @var{buffer} to the file with descriptor @var{filedes}. The data in | |
452 | @var{buffer} is not necessarily a character string and a null character is | |
453 | output like any other character. | |
454 | ||
455 | The return value is the number of bytes actually written. This may be | |
456 | @var{size}, but can always be smaller. Your program should always call | |
457 | @code{write} in a loop, iterating until all the data is written. | |
458 | ||
459 | Once @code{write} returns, the data is enqueued to be written and can be | |
460 | read back right away, but it is not necessarily written out to permanent | |
461 | storage immediately. You can use @code{fsync} when you need to be sure | |
462 | your data has been permanently stored before continuing. (It is more | |
463 | efficient for the system to batch up consecutive writes and do them all | |
464 | at once when convenient. Normally they will always be written to disk | |
a5a0310d UD |
465 | within a minute or less.) Modern systems provide another function |
466 | @code{fdatasync} which guarantees integrity only for the file data and | |
467 | is therefore faster. | |
468 | @c !!! xref fsync, fdatasync | |
2c6fe0bd | 469 | You can use the @code{O_FSYNC} open mode to make @code{write} always |
28f540f4 RM |
470 | store the data to disk before returning; @pxref{Operating Modes}. |
471 | ||
07435eb4 | 472 | In the case of an error, @code{write} returns @math{-1}. The following |
28f540f4 RM |
473 | @code{errno} error conditions are defined for this function: |
474 | ||
475 | @table @code | |
476 | @item EAGAIN | |
477 | Normally, @code{write} blocks until the write operation is complete. | |
478 | But if the @code{O_NONBLOCK} flag is set for the file (@pxref{Control | |
04b9968b | 479 | Operations}), it returns immediately without writing any data and |
28f540f4 RM |
480 | reports this error. An example of a situation that might cause the |
481 | process to block on output is writing to a terminal device that supports | |
482 | flow control, where output has been suspended by receipt of a STOP | |
483 | character. | |
484 | ||
485 | @strong{Compatibility Note:} Most versions of BSD Unix use a different | |
1f77f049 | 486 | error code for this: @code{EWOULDBLOCK}. In @theglibc{}, |
28f540f4 RM |
487 | @code{EWOULDBLOCK} is an alias for @code{EAGAIN}, so it doesn't matter |
488 | which name you use. | |
489 | ||
490 | On some systems, writing a large amount of data from a character special | |
491 | file can also fail with @code{EAGAIN} if the kernel cannot find enough | |
492 | physical memory to lock down the user's pages. This is limited to | |
493 | devices that transfer with direct memory access into the user's memory, | |
494 | which means it does not include terminals, since they always use | |
a7a93d50 JM |
495 | separate buffers inside the kernel. This problem does not arise on |
496 | @gnuhurdsystems{}. | |
28f540f4 RM |
497 | |
498 | @item EBADF | |
499 | The @var{filedes} argument is not a valid file descriptor, | |
500 | or is not open for writing. | |
501 | ||
502 | @item EFBIG | |
503 | The size of the file would become larger than the implementation can support. | |
504 | ||
505 | @item EINTR | |
506 | The @code{write} operation was interrupted by a signal while it was | |
04b9968b | 507 | blocked waiting for completion. A signal will not necessarily cause |
28f540f4 RM |
508 | @code{write} to return @code{EINTR}; it may instead result in a |
509 | successful @code{write} which writes fewer bytes than requested. | |
510 | @xref{Interrupted Primitives}. | |
511 | ||
512 | @item EIO | |
513 | For many devices, and for disk files, this error code indicates | |
514 | a hardware error. | |
515 | ||
516 | @item ENOSPC | |
517 | The device containing the file is full. | |
518 | ||
519 | @item EPIPE | |
520 | This error is returned when you try to write to a pipe or FIFO that | |
521 | isn't open for reading by any process. When this happens, a @code{SIGPIPE} | |
522 | signal is also sent to the process; see @ref{Signal Handling}. | |
7e583a52 RM |
523 | |
524 | @item EINVAL | |
525 | In some systems, when writing to a character or block device, position | |
526 | and size offsets must be aligned to a particular block size. This error | |
527 | indicates that the offsets were not properly aligned. | |
28f540f4 RM |
528 | @end table |
529 | ||
530 | Unless you have arranged to prevent @code{EINTR} failures, you should | |
531 | check @code{errno} after each failing call to @code{write}, and if the | |
532 | error was @code{EINTR}, you should simply repeat the call. | |
533 | @xref{Interrupted Primitives}. The easy way to do this is with the | |
534 | macro @code{TEMP_FAILURE_RETRY}, as follows: | |
535 | ||
536 | @smallexample | |
537 | nbytes = TEMP_FAILURE_RETRY (write (desc, buffer, count)); | |
538 | @end smallexample | |
539 | ||
b07d03e0 UD |
540 | Please note that there is no function named @code{write64}. This is not |
541 | necessary since this function does not directly modify or handle the | |
542 | possibly wide file offset. Since the kernel handles this state | |
543 | internally the @code{write} function can be used for all cases. | |
544 | ||
04b9968b | 545 | This function is a cancellation point in multi-threaded programs. This |
dfd2257a UD |
546 | is a problem if the thread allocates some resources (like memory, file |
547 | descriptors, semaphores or whatever) at the time @code{write} is | |
19e4c7dd | 548 | called. If the thread gets canceled these resources stay allocated |
04b9968b UD |
549 | until the program ends. To avoid this, calls to @code{write} should be |
550 | protected using cancellation handlers. | |
dfd2257a UD |
551 | @c ref pthread_cleanup_push / pthread_cleanup_pop |
552 | ||
28f540f4 RM |
553 | The @code{write} function is the underlying primitive for all of the |
554 | functions that write to streams, such as @code{fputc}. | |
555 | @end deftypefun | |
556 | ||
a5a0310d UD |
557 | @comment unistd.h |
558 | @comment Unix98 | |
559 | @deftypefun ssize_t pwrite (int @var{filedes}, const void *@var{buffer}, size_t @var{size}, off_t @var{offset}) | |
560 | The @code{pwrite} function is similar to the @code{write} function. The | |
04b9968b UD |
561 | first three arguments are identical, and the return values and error codes |
562 | also correspond. | |
a5a0310d UD |
563 | |
564 | The difference is the fourth argument and its handling. The data block | |
565 | is not written to the current position of the file descriptor | |
566 | @code{filedes}. Instead the data is written to the file starting at | |
567 | position @var{offset}. The position of the file descriptor itself is | |
04b9968b | 568 | not affected by the operation. The value is the same as before the call. |
a5a0310d | 569 | |
b07d03e0 UD |
570 | When the source file is compiled with @code{_FILE_OFFSET_BITS == 64} the |
571 | @code{pwrite} function is in fact @code{pwrite64} and the type | |
04b9968b | 572 | @code{off_t} has 64 bits, which makes it possible to handle files up to |
c756c71c | 573 | @math{2^63} bytes in length. |
b07d03e0 | 574 | |
a5a0310d UD |
575 | The return value of @code{pwrite} describes the number of written bytes. |
576 | In the error case it returns @math{-1} like @code{write} does and the | |
04b9968b UD |
577 | error codes are also the same, with these additions: |
578 | ||
a5a0310d UD |
579 | @table @code |
580 | @item EINVAL | |
581 | The value given for @var{offset} is negative and therefore illegal. | |
582 | ||
583 | @item ESPIPE | |
04b9968b | 584 | The file descriptor @var{filedes} is associated with a pipe or a FIFO and |
a5a0310d UD |
585 | this device does not allow positioning of the file pointer. |
586 | @end table | |
587 | ||
588 | The function is an extension defined in the Unix Single Specification | |
589 | version 2. | |
590 | @end deftypefun | |
591 | ||
b07d03e0 | 592 | @comment unistd.h |
a3a4a74e | 593 | @comment Unix98 |
b07d03e0 UD |
594 | @deftypefun ssize_t pwrite64 (int @var{filedes}, const void *@var{buffer}, size_t @var{size}, off64_t @var{offset}) |
595 | This function is similar to the @code{pwrite} function. The difference | |
596 | is that the @var{offset} parameter is of type @code{off64_t} instead of | |
04b9968b | 597 | @code{off_t} which makes it possible on 32 bit machines to address |
c756c71c | 598 | files larger than @math{2^31} bytes and up to @math{2^63} bytes. The |
b07d03e0 UD |
599 | file descriptor @code{filedes} must be opened using @code{open64} since |
600 | otherwise the large offsets possible with @code{off64_t} will lead to | |
601 | errors with a descriptor in small file mode. | |
602 | ||
c756c71c | 603 | When the source file is compiled using @code{_FILE_OFFSET_BITS == 64} on a |
04b9968b UD |
604 | 32 bit machine this function is actually available under the name |
605 | @code{pwrite} and so transparently replaces the 32 bit interface. | |
b07d03e0 UD |
606 | @end deftypefun |
607 | ||
a5a0310d | 608 | |
28f540f4 RM |
609 | @node File Position Primitive |
610 | @section Setting the File Position of a Descriptor | |
611 | ||
612 | Just as you can set the file position of a stream with @code{fseek}, you | |
613 | can set the file position of a descriptor with @code{lseek}. This | |
614 | specifies the position in the file for the next @code{read} or | |
615 | @code{write} operation. @xref{File Positioning}, for more information | |
616 | on the file position and what it means. | |
617 | ||
618 | To read the current file position value from a descriptor, use | |
619 | @code{lseek (@var{desc}, 0, SEEK_CUR)}. | |
620 | ||
621 | @cindex file positioning on a file descriptor | |
622 | @cindex positioning a file descriptor | |
623 | @cindex seeking on a file descriptor | |
624 | @comment unistd.h | |
625 | @comment POSIX.1 | |
626 | @deftypefun off_t lseek (int @var{filedes}, off_t @var{offset}, int @var{whence}) | |
627 | The @code{lseek} function is used to change the file position of the | |
628 | file with descriptor @var{filedes}. | |
629 | ||
630 | The @var{whence} argument specifies how the @var{offset} should be | |
04b9968b UD |
631 | interpreted, in the same way as for the @code{fseek} function, and it must |
632 | be one of the symbolic constants @code{SEEK_SET}, @code{SEEK_CUR}, or | |
28f540f4 RM |
633 | @code{SEEK_END}. |
634 | ||
635 | @table @code | |
636 | @item SEEK_SET | |
4dad7bab | 637 | Specifies that @var{offset} is a count of characters from the beginning |
28f540f4 RM |
638 | of the file. |
639 | ||
640 | @item SEEK_CUR | |
4dad7bab | 641 | Specifies that @var{offset} is a count of characters from the current |
28f540f4 RM |
642 | file position. This count may be positive or negative. |
643 | ||
644 | @item SEEK_END | |
4dad7bab | 645 | Specifies that @var{offset} is a count of characters from the end of |
28f540f4 RM |
646 | the file. A negative count specifies a position within the current |
647 | extent of the file; a positive count specifies a position past the | |
2c6fe0bd | 648 | current end. If you set the position past the current end, and |
28f540f4 | 649 | actually write data, you will extend the file with zeros up to that |
336dfb2d UD |
650 | position. |
651 | @end table | |
28f540f4 RM |
652 | |
653 | The return value from @code{lseek} is normally the resulting file | |
654 | position, measured in bytes from the beginning of the file. | |
655 | You can use this feature together with @code{SEEK_CUR} to read the | |
656 | current file position. | |
657 | ||
658 | If you want to append to the file, setting the file position to the | |
659 | current end of file with @code{SEEK_END} is not sufficient. Another | |
660 | process may write more data after you seek but before you write, | |
661 | extending the file so the position you write onto clobbers their data. | |
662 | Instead, use the @code{O_APPEND} operating mode; @pxref{Operating Modes}. | |
663 | ||
664 | You can set the file position past the current end of the file. This | |
665 | does not by itself make the file longer; @code{lseek} never changes the | |
666 | file. But subsequent output at that position will extend the file. | |
667 | Characters between the previous end of file and the new position are | |
668 | filled with zeros. Extending the file in this way can create a | |
669 | ``hole'': the blocks of zeros are not actually allocated on disk, so the | |
78759725 | 670 | file takes up less space than it appears to; it is then called a |
28f540f4 RM |
671 | ``sparse file''. |
672 | @cindex sparse files | |
673 | @cindex holes in files | |
674 | ||
675 | If the file position cannot be changed, or the operation is in some way | |
07435eb4 | 676 | invalid, @code{lseek} returns a value of @math{-1}. The following |
28f540f4 RM |
677 | @code{errno} error conditions are defined for this function: |
678 | ||
679 | @table @code | |
680 | @item EBADF | |
681 | The @var{filedes} is not a valid file descriptor. | |
682 | ||
683 | @item EINVAL | |
684 | The @var{whence} argument value is not valid, or the resulting | |
685 | file offset is not valid. A file offset is invalid. | |
686 | ||
687 | @item ESPIPE | |
688 | The @var{filedes} corresponds to an object that cannot be positioned, | |
689 | such as a pipe, FIFO or terminal device. (POSIX.1 specifies this error | |
a7a93d50 | 690 | only for pipes and FIFOs, but on @gnusystems{}, you always get |
28f540f4 RM |
691 | @code{ESPIPE} if the object is not seekable.) |
692 | @end table | |
693 | ||
b07d03e0 UD |
694 | When the source file is compiled with @code{_FILE_OFFSET_BITS == 64} the |
695 | @code{lseek} function is in fact @code{lseek64} and the type | |
696 | @code{off_t} has 64 bits which makes it possible to handle files up to | |
c756c71c | 697 | @math{2^63} bytes in length. |
b07d03e0 | 698 | |
04b9968b | 699 | This function is a cancellation point in multi-threaded programs. This |
dfd2257a UD |
700 | is a problem if the thread allocates some resources (like memory, file |
701 | descriptors, semaphores or whatever) at the time @code{lseek} is | |
19e4c7dd | 702 | called. If the thread gets canceled these resources stay allocated |
dfd2257a | 703 | until the program ends. To avoid this calls to @code{lseek} should be |
04b9968b | 704 | protected using cancellation handlers. |
dfd2257a UD |
705 | @c ref pthread_cleanup_push / pthread_cleanup_pop |
706 | ||
28f540f4 | 707 | The @code{lseek} function is the underlying primitive for the |
dfd2257a UD |
708 | @code{fseek}, @code{fseeko}, @code{ftell}, @code{ftello} and |
709 | @code{rewind} functions, which operate on streams instead of file | |
710 | descriptors. | |
28f540f4 RM |
711 | @end deftypefun |
712 | ||
b07d03e0 | 713 | @comment unistd.h |
a3a4a74e | 714 | @comment Unix98 |
b07d03e0 UD |
715 | @deftypefun off64_t lseek64 (int @var{filedes}, off64_t @var{offset}, int @var{whence}) |
716 | This function is similar to the @code{lseek} function. The difference | |
717 | is that the @var{offset} parameter is of type @code{off64_t} instead of | |
04b9968b | 718 | @code{off_t} which makes it possible on 32 bit machines to address |
c756c71c | 719 | files larger than @math{2^31} bytes and up to @math{2^63} bytes. The |
b07d03e0 UD |
720 | file descriptor @code{filedes} must be opened using @code{open64} since |
721 | otherwise the large offsets possible with @code{off64_t} will lead to | |
722 | errors with a descriptor in small file mode. | |
723 | ||
c756c71c | 724 | When the source file is compiled with @code{_FILE_OFFSET_BITS == 64} on a |
b07d03e0 | 725 | 32 bits machine this function is actually available under the name |
04b9968b | 726 | @code{lseek} and so transparently replaces the 32 bit interface. |
b07d03e0 UD |
727 | @end deftypefun |
728 | ||
28f540f4 | 729 | You can have multiple descriptors for the same file if you open the file |
2c6fe0bd | 730 | more than once, or if you duplicate a descriptor with @code{dup}. |
28f540f4 RM |
731 | Descriptors that come from separate calls to @code{open} have independent |
732 | file positions; using @code{lseek} on one descriptor has no effect on the | |
2c6fe0bd | 733 | other. For example, |
28f540f4 RM |
734 | |
735 | @smallexample | |
736 | @group | |
737 | @{ | |
738 | int d1, d2; | |
739 | char buf[4]; | |
740 | d1 = open ("foo", O_RDONLY); | |
741 | d2 = open ("foo", O_RDONLY); | |
742 | lseek (d1, 1024, SEEK_SET); | |
743 | read (d2, buf, 4); | |
744 | @} | |
745 | @end group | |
746 | @end smallexample | |
747 | ||
748 | @noindent | |
749 | will read the first four characters of the file @file{foo}. (The | |
750 | error-checking code necessary for a real program has been omitted here | |
751 | for brevity.) | |
752 | ||
753 | By contrast, descriptors made by duplication share a common file | |
754 | position with the original descriptor that was duplicated. Anything | |
755 | which alters the file position of one of the duplicates, including | |
756 | reading or writing data, affects all of them alike. Thus, for example, | |
757 | ||
758 | @smallexample | |
759 | @{ | |
760 | int d1, d2, d3; | |
761 | char buf1[4], buf2[4]; | |
762 | d1 = open ("foo", O_RDONLY); | |
763 | d2 = dup (d1); | |
764 | d3 = dup (d2); | |
765 | lseek (d3, 1024, SEEK_SET); | |
766 | read (d1, buf1, 4); | |
767 | read (d2, buf2, 4); | |
768 | @} | |
769 | @end smallexample | |
770 | ||
771 | @noindent | |
772 | will read four characters starting with the 1024'th character of | |
773 | @file{foo}, and then four more characters starting with the 1028'th | |
774 | character. | |
775 | ||
776 | @comment sys/types.h | |
777 | @comment POSIX.1 | |
778 | @deftp {Data Type} off_t | |
07e12bb3 JM |
779 | This is a signed integer type used to represent file sizes. In |
780 | @theglibc{}, this type is no narrower than @code{int}. | |
a3a4a74e UD |
781 | |
782 | If the source is compiled with @code{_FILE_OFFSET_BITS == 64} this type | |
783 | is transparently replaced by @code{off64_t}. | |
28f540f4 RM |
784 | @end deftp |
785 | ||
b07d03e0 | 786 | @comment sys/types.h |
a3a4a74e | 787 | @comment Unix98 |
b07d03e0 UD |
788 | @deftp {Data Type} off64_t |
789 | This type is used similar to @code{off_t}. The difference is that even | |
04b9968b | 790 | on 32 bit machines, where the @code{off_t} type would have 32 bits, |
b07d03e0 UD |
791 | @code{off64_t} has 64 bits and so is able to address files up to |
792 | @math{2^63} bytes in length. | |
a3a4a74e UD |
793 | |
794 | When compiling with @code{_FILE_OFFSET_BITS == 64} this type is | |
795 | available under the name @code{off_t}. | |
b07d03e0 UD |
796 | @end deftp |
797 | ||
28f540f4 RM |
798 | These aliases for the @samp{SEEK_@dots{}} constants exist for the sake |
799 | of compatibility with older BSD systems. They are defined in two | |
800 | different header files: @file{fcntl.h} and @file{sys/file.h}. | |
801 | ||
802 | @table @code | |
803 | @item L_SET | |
804 | An alias for @code{SEEK_SET}. | |
805 | ||
806 | @item L_INCR | |
807 | An alias for @code{SEEK_CUR}. | |
808 | ||
809 | @item L_XTND | |
810 | An alias for @code{SEEK_END}. | |
811 | @end table | |
812 | ||
813 | @node Descriptors and Streams | |
814 | @section Descriptors and Streams | |
815 | @cindex streams, and file descriptors | |
816 | @cindex converting file descriptor to stream | |
817 | @cindex extracting file descriptor from stream | |
818 | ||
819 | Given an open file descriptor, you can create a stream for it with the | |
820 | @code{fdopen} function. You can get the underlying file descriptor for | |
821 | an existing stream with the @code{fileno} function. These functions are | |
822 | declared in the header file @file{stdio.h}. | |
823 | @pindex stdio.h | |
824 | ||
825 | @comment stdio.h | |
826 | @comment POSIX.1 | |
827 | @deftypefun {FILE *} fdopen (int @var{filedes}, const char *@var{opentype}) | |
828 | The @code{fdopen} function returns a new stream for the file descriptor | |
829 | @var{filedes}. | |
830 | ||
831 | The @var{opentype} argument is interpreted in the same way as for the | |
832 | @code{fopen} function (@pxref{Opening Streams}), except that | |
a7a93d50 | 833 | the @samp{b} option is not permitted; this is because @gnusystems{} make no |
28f540f4 | 834 | distinction between text and binary files. Also, @code{"w"} and |
04b9968b | 835 | @code{"w+"} do not cause truncation of the file; these have an effect only |
28f540f4 RM |
836 | when opening a file, and in this case the file has already been opened. |
837 | You must make sure that the @var{opentype} argument matches the actual | |
838 | mode of the open file descriptor. | |
839 | ||
840 | The return value is the new stream. If the stream cannot be created | |
841 | (for example, if the modes for the file indicated by the file descriptor | |
842 | do not permit the access specified by the @var{opentype} argument), a | |
843 | null pointer is returned instead. | |
844 | ||
845 | In some other systems, @code{fdopen} may fail to detect that the modes | |
846 | for file descriptor do not permit the access specified by | |
1f77f049 | 847 | @code{opentype}. @Theglibc{} always checks for this. |
28f540f4 RM |
848 | @end deftypefun |
849 | ||
850 | For an example showing the use of the @code{fdopen} function, | |
851 | see @ref{Creating a Pipe}. | |
852 | ||
853 | @comment stdio.h | |
854 | @comment POSIX.1 | |
855 | @deftypefun int fileno (FILE *@var{stream}) | |
856 | This function returns the file descriptor associated with the stream | |
857 | @var{stream}. If an error is detected (for example, if the @var{stream} | |
858 | is not valid) or if @var{stream} does not do I/O to a file, | |
07435eb4 | 859 | @code{fileno} returns @math{-1}. |
28f540f4 RM |
860 | @end deftypefun |
861 | ||
7b4161bb UD |
862 | @comment stdio.h |
863 | @comment GNU | |
864 | @deftypefun int fileno_unlocked (FILE *@var{stream}) | |
865 | The @code{fileno_unlocked} function is equivalent to the @code{fileno} | |
866 | function except that it does not implicitly lock the stream if the state | |
867 | is @code{FSETLOCKING_INTERNAL}. | |
868 | ||
869 | This function is a GNU extension. | |
870 | @end deftypefun | |
871 | ||
28f540f4 RM |
872 | @cindex standard file descriptors |
873 | @cindex file descriptors, standard | |
874 | There are also symbolic constants defined in @file{unistd.h} for the | |
875 | file descriptors belonging to the standard streams @code{stdin}, | |
876 | @code{stdout}, and @code{stderr}; see @ref{Standard Streams}. | |
877 | @pindex unistd.h | |
878 | ||
879 | @comment unistd.h | |
880 | @comment POSIX.1 | |
881 | @table @code | |
882 | @item STDIN_FILENO | |
883 | @vindex STDIN_FILENO | |
884 | This macro has value @code{0}, which is the file descriptor for | |
885 | standard input. | |
886 | @cindex standard input file descriptor | |
887 | ||
888 | @comment unistd.h | |
889 | @comment POSIX.1 | |
890 | @item STDOUT_FILENO | |
891 | @vindex STDOUT_FILENO | |
892 | This macro has value @code{1}, which is the file descriptor for | |
893 | standard output. | |
894 | @cindex standard output file descriptor | |
895 | ||
896 | @comment unistd.h | |
897 | @comment POSIX.1 | |
898 | @item STDERR_FILENO | |
899 | @vindex STDERR_FILENO | |
900 | This macro has value @code{2}, which is the file descriptor for | |
901 | standard error output. | |
902 | @end table | |
903 | @cindex standard error file descriptor | |
904 | ||
905 | @node Stream/Descriptor Precautions | |
906 | @section Dangers of Mixing Streams and Descriptors | |
907 | @cindex channels | |
908 | @cindex streams and descriptors | |
909 | @cindex descriptors and streams | |
910 | @cindex mixing descriptors and streams | |
911 | ||
912 | You can have multiple file descriptors and streams (let's call both | |
913 | streams and descriptors ``channels'' for short) connected to the same | |
914 | file, but you must take care to avoid confusion between channels. There | |
915 | are two cases to consider: @dfn{linked} channels that share a single | |
916 | file position value, and @dfn{independent} channels that have their own | |
917 | file positions. | |
918 | ||
919 | It's best to use just one channel in your program for actual data | |
920 | transfer to any given file, except when all the access is for input. | |
921 | For example, if you open a pipe (something you can only do at the file | |
922 | descriptor level), either do all I/O with the descriptor, or construct a | |
923 | stream from the descriptor with @code{fdopen} and then do all I/O with | |
924 | the stream. | |
925 | ||
926 | @menu | |
927 | * Linked Channels:: Dealing with channels sharing a file position. | |
928 | * Independent Channels:: Dealing with separately opened, unlinked channels. | |
2c6fe0bd | 929 | * Cleaning Streams:: Cleaning a stream makes it safe to use |
28f540f4 RM |
930 | another channel. |
931 | @end menu | |
932 | ||
933 | @node Linked Channels | |
934 | @subsection Linked Channels | |
935 | @cindex linked channels | |
936 | ||
937 | Channels that come from a single opening share the same file position; | |
938 | we call them @dfn{linked} channels. Linked channels result when you | |
939 | make a stream from a descriptor using @code{fdopen}, when you get a | |
940 | descriptor from a stream with @code{fileno}, when you copy a descriptor | |
941 | with @code{dup} or @code{dup2}, and when descriptors are inherited | |
942 | during @code{fork}. For files that don't support random access, such as | |
943 | terminals and pipes, @emph{all} channels are effectively linked. On | |
944 | random-access files, all append-type output streams are effectively | |
945 | linked to each other. | |
946 | ||
947 | @cindex cleaning up a stream | |
0295d266 UD |
948 | If you have been using a stream for I/O (or have just opened the stream), |
949 | and you want to do I/O using | |
28f540f4 RM |
950 | another channel (either a stream or a descriptor) that is linked to it, |
951 | you must first @dfn{clean up} the stream that you have been using. | |
952 | @xref{Cleaning Streams}. | |
953 | ||
954 | Terminating a process, or executing a new program in the process, | |
955 | destroys all the streams in the process. If descriptors linked to these | |
956 | streams persist in other processes, their file positions become | |
957 | undefined as a result. To prevent this, you must clean up the streams | |
958 | before destroying them. | |
959 | ||
960 | @node Independent Channels | |
961 | @subsection Independent Channels | |
962 | @cindex independent channels | |
963 | ||
964 | When you open channels (streams or descriptors) separately on a seekable | |
965 | file, each channel has its own file position. These are called | |
966 | @dfn{independent channels}. | |
967 | ||
968 | The system handles each channel independently. Most of the time, this | |
969 | is quite predictable and natural (especially for input): each channel | |
970 | can read or write sequentially at its own place in the file. However, | |
971 | if some of the channels are streams, you must take these precautions: | |
972 | ||
973 | @itemize @bullet | |
974 | @item | |
975 | You should clean an output stream after use, before doing anything else | |
976 | that might read or write from the same part of the file. | |
977 | ||
978 | @item | |
979 | You should clean an input stream before reading data that may have been | |
980 | modified using an independent channel. Otherwise, you might read | |
981 | obsolete data that had been in the stream's buffer. | |
982 | @end itemize | |
983 | ||
984 | If you do output to one channel at the end of the file, this will | |
985 | certainly leave the other independent channels positioned somewhere | |
986 | before the new end. You cannot reliably set their file positions to the | |
987 | new end of file before writing, because the file can always be extended | |
988 | by another process between when you set the file position and when you | |
989 | write the data. Instead, use an append-type descriptor or stream; they | |
990 | always output at the current end of the file. In order to make the | |
991 | end-of-file position accurate, you must clean the output channel you | |
992 | were using, if it is a stream. | |
993 | ||
994 | It's impossible for two channels to have separate file pointers for a | |
995 | file that doesn't support random access. Thus, channels for reading or | |
996 | writing such files are always linked, never independent. Append-type | |
997 | channels are also always linked. For these channels, follow the rules | |
998 | for linked channels; see @ref{Linked Channels}. | |
999 | ||
1000 | @node Cleaning Streams | |
1001 | @subsection Cleaning Streams | |
1002 | ||
6664049b | 1003 | You can use @code{fflush} to clean a stream in most |
28f540f4 RM |
1004 | cases. |
1005 | ||
6664049b | 1006 | You can skip the @code{fflush} if you know the stream |
28f540f4 RM |
1007 | is already clean. A stream is clean whenever its buffer is empty. For |
1008 | example, an unbuffered stream is always clean. An input stream that is | |
1009 | at end-of-file is clean. A line-buffered stream is clean when the last | |
0295d266 UD |
1010 | character output was a newline. However, a just-opened input stream |
1011 | might not be clean, as its input buffer might not be empty. | |
28f540f4 RM |
1012 | |
1013 | There is one case in which cleaning a stream is impossible on most | |
1014 | systems. This is when the stream is doing input from a file that is not | |
1015 | random-access. Such streams typically read ahead, and when the file is | |
1016 | not random access, there is no way to give back the excess data already | |
1017 | read. When an input stream reads from a random-access file, | |
1018 | @code{fflush} does clean the stream, but leaves the file pointer at an | |
1019 | unpredictable place; you must set the file pointer before doing any | |
6664049b | 1020 | further I/O. |
28f540f4 RM |
1021 | |
1022 | Closing an output-only stream also does @code{fflush}, so this is a | |
6664049b | 1023 | valid way of cleaning an output stream. |
28f540f4 RM |
1024 | |
1025 | You need not clean a stream before using its descriptor for control | |
1026 | operations such as setting terminal modes; these operations don't affect | |
1027 | the file position and are not affected by it. You can use any | |
1028 | descriptor for these operations, and all channels are affected | |
1029 | simultaneously. However, text already ``output'' to a stream but still | |
1030 | buffered by the stream will be subject to the new terminal modes when | |
1031 | subsequently flushed. To make sure ``past'' output is covered by the | |
1032 | terminal settings that were in effect at the time, flush the output | |
1033 | streams for that terminal before setting the modes. @xref{Terminal | |
1034 | Modes}. | |
1035 | ||
07435eb4 UD |
1036 | @node Scatter-Gather |
1037 | @section Fast Scatter-Gather I/O | |
1038 | @cindex scatter-gather | |
1039 | ||
1040 | Some applications may need to read or write data to multiple buffers, | |
04b9968b | 1041 | which are separated in memory. Although this can be done easily enough |
19e4c7dd | 1042 | with multiple calls to @code{read} and @code{write}, it is inefficient |
07435eb4 UD |
1043 | because there is overhead associated with each kernel call. |
1044 | ||
1045 | Instead, many platforms provide special high-speed primitives to perform | |
1f77f049 JM |
1046 | these @dfn{scatter-gather} operations in a single kernel call. @Theglibc{} |
1047 | will provide an emulation on any system that lacks these | |
07435eb4 UD |
1048 | primitives, so they are not a portability threat. They are defined in |
1049 | @code{sys/uio.h}. | |
1050 | ||
1051 | These functions are controlled with arrays of @code{iovec} structures, | |
1052 | which describe the location and size of each buffer. | |
1053 | ||
4c450556 UD |
1054 | @comment sys/uio.h |
1055 | @comment BSD | |
07435eb4 UD |
1056 | @deftp {Data Type} {struct iovec} |
1057 | ||
1058 | The @code{iovec} structure describes a buffer. It contains two fields: | |
1059 | ||
1060 | @table @code | |
1061 | ||
1062 | @item void *iov_base | |
1063 | Contains the address of a buffer. | |
1064 | ||
1065 | @item size_t iov_len | |
1066 | Contains the length of the buffer. | |
1067 | ||
1068 | @end table | |
1069 | @end deftp | |
1070 | ||
4c450556 UD |
1071 | @comment sys/uio.h |
1072 | @comment BSD | |
07435eb4 UD |
1073 | @deftypefun ssize_t readv (int @var{filedes}, const struct iovec *@var{vector}, int @var{count}) |
1074 | ||
1075 | The @code{readv} function reads data from @var{filedes} and scatters it | |
1076 | into the buffers described in @var{vector}, which is taken to be | |
1077 | @var{count} structures long. As each buffer is filled, data is sent to the | |
1078 | next. | |
1079 | ||
1080 | Note that @code{readv} is not guaranteed to fill all the buffers. | |
1081 | It may stop at any point, for the same reasons @code{read} would. | |
1082 | ||
1083 | The return value is a count of bytes (@emph{not} buffers) read, @math{0} | |
1084 | indicating end-of-file, or @math{-1} indicating an error. The possible | |
1085 | errors are the same as in @code{read}. | |
1086 | ||
1087 | @end deftypefun | |
1088 | ||
4c450556 UD |
1089 | @comment sys/uio.h |
1090 | @comment BSD | |
07435eb4 UD |
1091 | @deftypefun ssize_t writev (int @var{filedes}, const struct iovec *@var{vector}, int @var{count}) |
1092 | ||
1093 | The @code{writev} function gathers data from the buffers described in | |
1094 | @var{vector}, which is taken to be @var{count} structures long, and writes | |
1095 | them to @code{filedes}. As each buffer is written, it moves on to the | |
1096 | next. | |
1097 | ||
1098 | Like @code{readv}, @code{writev} may stop midstream under the same | |
1099 | conditions @code{write} would. | |
1100 | ||
1101 | The return value is a count of bytes written, or @math{-1} indicating an | |
1102 | error. The possible errors are the same as in @code{write}. | |
1103 | ||
1104 | @end deftypefun | |
1105 | ||
1106 | @c Note - I haven't read this anywhere. I surmised it from my knowledge | |
1107 | @c of computer science. Thus, there could be subtleties I'm missing. | |
1108 | ||
1109 | Note that if the buffers are small (under about 1kB), high-level streams | |
1110 | may be easier to use than these functions. However, @code{readv} and | |
1111 | @code{writev} are more efficient when the individual buffers themselves | |
1112 | (as opposed to the total output), are large. In that case, a high-level | |
1113 | stream would not be able to cache the data effectively. | |
1114 | ||
1115 | @node Memory-mapped I/O | |
1116 | @section Memory-mapped I/O | |
1117 | ||
1118 | On modern operating systems, it is possible to @dfn{mmap} (pronounced | |
1119 | ``em-map'') a file to a region of memory. When this is done, the file can | |
1120 | be accessed just like an array in the program. | |
1121 | ||
19e4c7dd | 1122 | This is more efficient than @code{read} or @code{write}, as only the regions |
04b9968b | 1123 | of the file that a program actually accesses are loaded. Accesses to |
07435eb4 UD |
1124 | not-yet-loaded parts of the mmapped region are handled in the same way as |
1125 | swapped out pages. | |
1126 | ||
b642f101 UD |
1127 | Since mmapped pages can be stored back to their file when physical |
1128 | memory is low, it is possible to mmap files orders of magnitude larger | |
1129 | than both the physical memory @emph{and} swap space. The only limit is | |
1130 | address space. The theoretical limit is 4GB on a 32-bit machine - | |
1131 | however, the actual limit will be smaller since some areas will be | |
1132 | reserved for other purposes. If the LFS interface is used the file size | |
1133 | on 32-bit systems is not limited to 2GB (offsets are signed which | |
1134 | reduces the addressable area of 4GB by half); the full 64-bit are | |
1135 | available. | |
07435eb4 UD |
1136 | |
1137 | Memory mapping only works on entire pages of memory. Thus, addresses | |
1138 | for mapping must be page-aligned, and length values will be rounded up. | |
1139 | To determine the size of a page the machine uses one should use | |
1140 | ||
b642f101 | 1141 | @vindex _SC_PAGESIZE |
07435eb4 UD |
1142 | @smallexample |
1143 | size_t page_size = (size_t) sysconf (_SC_PAGESIZE); | |
1144 | @end smallexample | |
1145 | ||
b642f101 | 1146 | @noindent |
07435eb4 UD |
1147 | These functions are declared in @file{sys/mman.h}. |
1148 | ||
4c450556 UD |
1149 | @comment sys/mman.h |
1150 | @comment POSIX | |
cc6e48bc | 1151 | @deftypefun {void *} mmap (void *@var{address}, size_t @var{length}, int @var{protect}, int @var{flags}, int @var{filedes}, off_t @var{offset}) |
07435eb4 UD |
1152 | |
1153 | The @code{mmap} function creates a new mapping, connected to bytes | |
b73147d0 | 1154 | (@var{offset}) to (@var{offset} + @var{length} - 1) in the file open on |
b61345a1 UD |
1155 | @var{filedes}. A new reference for the file specified by @var{filedes} |
1156 | is created, which is not removed by closing the file. | |
07435eb4 UD |
1157 | |
1158 | @var{address} gives a preferred starting address for the mapping. | |
1159 | @code{NULL} expresses no preference. Any previous mapping at that | |
1160 | address is automatically removed. The address you give may still be | |
1161 | changed, unless you use the @code{MAP_FIXED} flag. | |
1162 | ||
1163 | @vindex PROT_READ | |
1164 | @vindex PROT_WRITE | |
1165 | @vindex PROT_EXEC | |
1166 | @var{protect} contains flags that control what kind of access is | |
1167 | permitted. They include @code{PROT_READ}, @code{PROT_WRITE}, and | |
1168 | @code{PROT_EXEC}, which permit reading, writing, and execution, | |
1169 | respectively. Inappropriate access will cause a segfault (@pxref{Program | |
1170 | Error Signals}). | |
1171 | ||
1172 | Note that most hardware designs cannot support write permission without | |
1173 | read permission, and many do not distinguish read and execute permission. | |
49c091e5 | 1174 | Thus, you may receive wider permissions than you ask for, and mappings of |
07435eb4 UD |
1175 | write-only files may be denied even if you do not use @code{PROT_READ}. |
1176 | ||
1177 | @var{flags} contains flags that control the nature of the map. | |
1178 | One of @code{MAP_SHARED} or @code{MAP_PRIVATE} must be specified. | |
1179 | ||
1180 | They include: | |
1181 | ||
1182 | @vtable @code | |
1183 | @item MAP_PRIVATE | |
1184 | This specifies that writes to the region should never be written back | |
1185 | to the attached file. Instead, a copy is made for the process, and the | |
1186 | region will be swapped normally if memory runs low. No other process will | |
1187 | see the changes. | |
1188 | ||
1189 | Since private mappings effectively revert to ordinary memory | |
1190 | when written to, you must have enough virtual memory for a copy of | |
1191 | the entire mmapped region if you use this mode with @code{PROT_WRITE}. | |
1192 | ||
1193 | @item MAP_SHARED | |
1194 | This specifies that writes to the region will be written back to the | |
1195 | file. Changes made will be shared immediately with other processes | |
1196 | mmaping the same file. | |
1197 | ||
1198 | Note that actual writing may take place at any time. You need to use | |
1199 | @code{msync}, described below, if it is important that other processes | |
1200 | using conventional I/O get a consistent view of the file. | |
1201 | ||
1202 | @item MAP_FIXED | |
1203 | This forces the system to use the exact mapping address specified in | |
1204 | @var{address} and fail if it can't. | |
1205 | ||
1206 | @c One of these is official - the other is obviously an obsolete synonym | |
1207 | @c Which is which? | |
1208 | @item MAP_ANONYMOUS | |
1209 | @itemx MAP_ANON | |
1210 | This flag tells the system to create an anonymous mapping, not connected | |
1211 | to a file. @var{filedes} and @var{off} are ignored, and the region is | |
1212 | initialized with zeros. | |
1213 | ||
1214 | Anonymous maps are used as the basic primitive to extend the heap on some | |
1215 | systems. They are also useful to share data between multiple tasks | |
1216 | without creating a file. | |
1217 | ||
49c091e5 | 1218 | On some systems using private anonymous mmaps is more efficient than using |
1f77f049 | 1219 | @code{malloc} for large blocks. This is not an issue with @theglibc{}, |
07435eb4 UD |
1220 | as the included @code{malloc} automatically uses @code{mmap} where appropriate. |
1221 | ||
1222 | @c Linux has some other MAP_ options, which I have not discussed here. | |
1223 | @c MAP_DENYWRITE, MAP_EXECUTABLE and MAP_GROWSDOWN don't seem applicable to | |
1224 | @c user programs (and I don't understand the last two). MAP_LOCKED does | |
1225 | @c not appear to be implemented. | |
1226 | ||
1227 | @end vtable | |
1228 | ||
1229 | @code{mmap} returns the address of the new mapping, or @math{-1} for an | |
1230 | error. | |
1231 | ||
1232 | Possible errors include: | |
1233 | ||
1234 | @table @code | |
1235 | ||
1236 | @item EINVAL | |
1237 | ||
1238 | Either @var{address} was unusable, or inconsistent @var{flags} were | |
1239 | given. | |
1240 | ||
1241 | @item EACCES | |
1242 | ||
1243 | @var{filedes} was not open for the type of access specified in @var{protect}. | |
1244 | ||
1245 | @item ENOMEM | |
1246 | ||
1247 | Either there is not enough memory for the operation, or the process is | |
1248 | out of address space. | |
1249 | ||
1250 | @item ENODEV | |
1251 | ||
1252 | This file is of a type that doesn't support mapping. | |
1253 | ||
1254 | @item ENOEXEC | |
1255 | ||
1256 | The file is on a filesystem that doesn't support mapping. | |
1257 | ||
1258 | @c On Linux, EAGAIN will appear if the file has a conflicting mandatory lock. | |
1259 | @c However mandatory locks are not discussed in this manual. | |
1260 | @c | |
1261 | @c Similarly, ETXTBSY will occur if the MAP_DENYWRITE flag (not documented | |
1262 | @c here) is used and the file is already open for writing. | |
1263 | ||
1264 | @end table | |
1265 | ||
1266 | @end deftypefun | |
1267 | ||
4c450556 UD |
1268 | @comment sys/mman.h |
1269 | @comment LFS | |
cc6e48bc | 1270 | @deftypefun {void *} mmap64 (void *@var{address}, size_t @var{length}, int @var{protect}, int @var{flags}, int @var{filedes}, off64_t @var{offset}) |
b642f101 UD |
1271 | The @code{mmap64} function is equivalent to the @code{mmap} function but |
1272 | the @var{offset} parameter is of type @code{off64_t}. On 32-bit systems | |
1273 | this allows the file associated with the @var{filedes} descriptor to be | |
1274 | larger than 2GB. @var{filedes} must be a descriptor returned from a | |
1275 | call to @code{open64} or @code{fopen64} and @code{freopen64} where the | |
1276 | descriptor is retrieved with @code{fileno}. | |
1277 | ||
1278 | When the sources are translated with @code{_FILE_OFFSET_BITS == 64} this | |
1279 | function is actually available under the name @code{mmap}. I.e., the | |
1280 | new, extended API using 64 bit file sizes and offsets transparently | |
1281 | replaces the old API. | |
1282 | @end deftypefun | |
1283 | ||
4c450556 UD |
1284 | @comment sys/mman.h |
1285 | @comment POSIX | |
07435eb4 UD |
1286 | @deftypefun int munmap (void *@var{addr}, size_t @var{length}) |
1287 | ||
1288 | @code{munmap} removes any memory maps from (@var{addr}) to (@var{addr} + | |
1289 | @var{length}). @var{length} should be the length of the mapping. | |
1290 | ||
04b9968b | 1291 | It is safe to unmap multiple mappings in one command, or include unmapped |
07435eb4 | 1292 | space in the range. It is also possible to unmap only part of an existing |
04b9968b | 1293 | mapping. However, only entire pages can be removed. If @var{length} is not |
07435eb4 UD |
1294 | an even number of pages, it will be rounded up. |
1295 | ||
1296 | It returns @math{0} for success and @math{-1} for an error. | |
1297 | ||
1298 | One error is possible: | |
1299 | ||
1300 | @table @code | |
1301 | ||
1302 | @item EINVAL | |
04b9968b | 1303 | The memory range given was outside the user mmap range or wasn't page |
07435eb4 UD |
1304 | aligned. |
1305 | ||
1306 | @end table | |
1307 | ||
1308 | @end deftypefun | |
1309 | ||
4c450556 UD |
1310 | @comment sys/mman.h |
1311 | @comment POSIX | |
07435eb4 UD |
1312 | @deftypefun int msync (void *@var{address}, size_t @var{length}, int @var{flags}) |
1313 | ||
1314 | When using shared mappings, the kernel can write the file at any time | |
1315 | before the mapping is removed. To be certain data has actually been | |
49c091e5 UD |
1316 | written to the file and will be accessible to non-memory-mapped I/O, it |
1317 | is necessary to use this function. | |
07435eb4 UD |
1318 | |
1319 | It operates on the region @var{address} to (@var{address} + @var{length}). | |
1320 | It may be used on part of a mapping or multiple mappings, however the | |
1321 | region given should not contain any unmapped space. | |
1322 | ||
1323 | @var{flags} can contain some options: | |
1324 | ||
1325 | @vtable @code | |
1326 | ||
1327 | @item MS_SYNC | |
1328 | ||
1329 | This flag makes sure the data is actually written @emph{to disk}. | |
1330 | Normally @code{msync} only makes sure that accesses to a file with | |
1331 | conventional I/O reflect the recent changes. | |
1332 | ||
1333 | @item MS_ASYNC | |
1334 | ||
1335 | This tells @code{msync} to begin the synchronization, but not to wait for | |
1336 | it to complete. | |
1337 | ||
1338 | @c Linux also has MS_INVALIDATE, which I don't understand. | |
1339 | ||
1340 | @end vtable | |
1341 | ||
1342 | @code{msync} returns @math{0} for success and @math{-1} for | |
1343 | error. Errors include: | |
1344 | ||
1345 | @table @code | |
1346 | ||
1347 | @item EINVAL | |
1348 | An invalid region was given, or the @var{flags} were invalid. | |
1349 | ||
1350 | @item EFAULT | |
1351 | There is no existing mapping in at least part of the given region. | |
1352 | ||
1353 | @end table | |
1354 | ||
1355 | @end deftypefun | |
1356 | ||
4c450556 UD |
1357 | @comment sys/mman.h |
1358 | @comment GNU | |
07435eb4 UD |
1359 | @deftypefun {void *} mremap (void *@var{address}, size_t @var{length}, size_t @var{new_length}, int @var{flag}) |
1360 | ||
1361 | This function can be used to change the size of an existing memory | |
1362 | area. @var{address} and @var{length} must cover a region entirely mapped | |
1363 | in the same @code{mmap} statement. A new mapping with the same | |
04b9968b | 1364 | characteristics will be returned with the length @var{new_length}. |
07435eb4 UD |
1365 | |
1366 | One option is possible, @code{MREMAP_MAYMOVE}. If it is given in | |
1367 | @var{flags}, the system may remove the existing mapping and create a new | |
1368 | one of the desired length in another location. | |
1369 | ||
1370 | The address of the resulting mapping is returned, or @math{-1}. Possible | |
1371 | error codes include: | |
1372 | ||
07435eb4 UD |
1373 | @table @code |
1374 | ||
1375 | @item EFAULT | |
1376 | There is no existing mapping in at least part of the original region, or | |
1377 | the region covers two or more distinct mappings. | |
1378 | ||
1379 | @item EINVAL | |
1380 | The address given is misaligned or inappropriate. | |
1381 | ||
1382 | @item EAGAIN | |
1383 | The region has pages locked, and if extended it would exceed the | |
1384 | process's resource limit for locked pages. @xref{Limits on Resources}. | |
1385 | ||
1386 | @item ENOMEM | |
19e4c7dd | 1387 | The region is private writable, and insufficient virtual memory is |
07435eb4 UD |
1388 | available to extend it. Also, this error will occur if |
1389 | @code{MREMAP_MAYMOVE} is not given and the extension would collide with | |
1390 | another mapped region. | |
1391 | ||
1392 | @end table | |
1393 | @end deftypefun | |
1394 | ||
04b9968b UD |
1395 | This function is only available on a few systems. Except for performing |
1396 | optional optimizations one should not rely on this function. | |
1397 | ||
07435eb4 UD |
1398 | Not all file descriptors may be mapped. Sockets, pipes, and most devices |
1399 | only allow sequential access and do not fit into the mapping abstraction. | |
1400 | In addition, some regular files may not be mmapable, and older kernels may | |
1401 | not support mapping at all. Thus, programs using @code{mmap} should | |
1402 | have a fallback method to use should it fail. @xref{Mmap,,,standards,GNU | |
1403 | Coding Standards}. | |
1404 | ||
0bc93a2f AJ |
1405 | @comment sys/mman.h |
1406 | @comment POSIX | |
1407 | @deftypefun int madvise (void *@var{addr}, size_t @var{length}, int @var{advice}) | |
1408 | ||
1409 | This function can be used to provide the system with @var{advice} about | |
1410 | the intended usage patterns of the memory region starting at @var{addr} | |
1411 | and extending @var{length} bytes. | |
1412 | ||
1413 | The valid BSD values for @var{advice} are: | |
1414 | ||
1415 | @table @code | |
1416 | ||
1417 | @item MADV_NORMAL | |
1418 | The region should receive no further special treatment. | |
1419 | ||
1420 | @item MADV_RANDOM | |
1421 | The region will be accessed via random page references. The kernel | |
1422 | should page-in the minimal number of pages for each page fault. | |
1423 | ||
1424 | @item MADV_SEQUENTIAL | |
1425 | The region will be accessed via sequential page references. This | |
1426 | may cause the kernel to aggressively read-ahead, expecting further | |
1427 | sequential references after any page fault within this region. | |
1428 | ||
1429 | @item MADV_WILLNEED | |
1430 | The region will be needed. The pages within this region may | |
1431 | be pre-faulted in by the kernel. | |
1432 | ||
1433 | @item MADV_DONTNEED | |
1434 | The region is no longer needed. The kernel may free these pages, | |
1435 | causing any changes to the pages to be lost, as well as swapped | |
1436 | out pages to be discarded. | |
1437 | ||
1438 | @end table | |
1439 | ||
1440 | The POSIX names are slightly different, but with the same meanings: | |
1441 | ||
1442 | @table @code | |
1443 | ||
1444 | @item POSIX_MADV_NORMAL | |
1445 | This corresponds with BSD's @code{MADV_NORMAL}. | |
1446 | ||
1447 | @item POSIX_MADV_RANDOM | |
1448 | This corresponds with BSD's @code{MADV_RANDOM}. | |
1449 | ||
1450 | @item POSIX_MADV_SEQUENTIAL | |
1451 | This corresponds with BSD's @code{MADV_SEQUENTIAL}. | |
1452 | ||
1453 | @item POSIX_MADV_WILLNEED | |
1454 | This corresponds with BSD's @code{MADV_WILLNEED}. | |
1455 | ||
1456 | @item POSIX_MADV_DONTNEED | |
1457 | This corresponds with BSD's @code{MADV_DONTNEED}. | |
1458 | ||
1459 | @end table | |
1460 | ||
bb4e6db2 | 1461 | @code{madvise} returns @math{0} for success and @math{-1} for |
0bc93a2f AJ |
1462 | error. Errors include: |
1463 | @table @code | |
1464 | ||
1465 | @item EINVAL | |
1466 | An invalid region was given, or the @var{advice} was invalid. | |
1467 | ||
1468 | @item EFAULT | |
1469 | There is no existing mapping in at least part of the given region. | |
1470 | ||
1471 | @end table | |
1472 | @end deftypefun | |
07435eb4 | 1473 | |
28f540f4 RM |
1474 | @node Waiting for I/O |
1475 | @section Waiting for Input or Output | |
1476 | @cindex waiting for input or output | |
1477 | @cindex multiplexing input | |
1478 | @cindex input from multiple files | |
1479 | ||
1480 | Sometimes a program needs to accept input on multiple input channels | |
1481 | whenever input arrives. For example, some workstations may have devices | |
1482 | such as a digitizing tablet, function button box, or dial box that are | |
1483 | connected via normal asynchronous serial interfaces; good user interface | |
1484 | style requires responding immediately to input on any device. Another | |
1485 | example is a program that acts as a server to several other processes | |
1486 | via pipes or sockets. | |
1487 | ||
1488 | You cannot normally use @code{read} for this purpose, because this | |
1489 | blocks the program until input is available on one particular file | |
1490 | descriptor; input on other channels won't wake it up. You could set | |
1491 | nonblocking mode and poll each file descriptor in turn, but this is very | |
1492 | inefficient. | |
1493 | ||
1494 | A better solution is to use the @code{select} function. This blocks the | |
1495 | program until input or output is ready on a specified set of file | |
1496 | descriptors, or until a timer expires, whichever comes first. This | |
1497 | facility is declared in the header file @file{sys/types.h}. | |
1498 | @pindex sys/types.h | |
1499 | ||
1500 | In the case of a server socket (@pxref{Listening}), we say that | |
1501 | ``input'' is available when there are pending connections that could be | |
1502 | accepted (@pxref{Accepting Connections}). @code{accept} for server | |
1503 | sockets blocks and interacts with @code{select} just as @code{read} does | |
1504 | for normal input. | |
1505 | ||
1506 | @cindex file descriptor sets, for @code{select} | |
1507 | The file descriptor sets for the @code{select} function are specified | |
1508 | as @code{fd_set} objects. Here is the description of the data type | |
1509 | and some macros for manipulating these objects. | |
1510 | ||
1511 | @comment sys/types.h | |
1512 | @comment BSD | |
1513 | @deftp {Data Type} fd_set | |
1514 | The @code{fd_set} data type represents file descriptor sets for the | |
1515 | @code{select} function. It is actually a bit array. | |
1516 | @end deftp | |
1517 | ||
1518 | @comment sys/types.h | |
1519 | @comment BSD | |
1520 | @deftypevr Macro int FD_SETSIZE | |
1521 | The value of this macro is the maximum number of file descriptors that a | |
1522 | @code{fd_set} object can hold information about. On systems with a | |
1523 | fixed maximum number, @code{FD_SETSIZE} is at least that number. On | |
1524 | some systems, including GNU, there is no absolute limit on the number of | |
1525 | descriptors open, but this macro still has a constant value which | |
1526 | controls the number of bits in an @code{fd_set}; if you get a file | |
1527 | descriptor with a value as high as @code{FD_SETSIZE}, you cannot put | |
1528 | that descriptor into an @code{fd_set}. | |
1529 | @end deftypevr | |
1530 | ||
1531 | @comment sys/types.h | |
1532 | @comment BSD | |
1533 | @deftypefn Macro void FD_ZERO (fd_set *@var{set}) | |
1534 | This macro initializes the file descriptor set @var{set} to be the | |
1535 | empty set. | |
1536 | @end deftypefn | |
1537 | ||
1538 | @comment sys/types.h | |
1539 | @comment BSD | |
1540 | @deftypefn Macro void FD_SET (int @var{filedes}, fd_set *@var{set}) | |
1541 | This macro adds @var{filedes} to the file descriptor set @var{set}. | |
d9997a45 UD |
1542 | |
1543 | The @var{filedes} parameter must not have side effects since it is | |
1544 | evaluated more than once. | |
28f540f4 RM |
1545 | @end deftypefn |
1546 | ||
1547 | @comment sys/types.h | |
1548 | @comment BSD | |
1549 | @deftypefn Macro void FD_CLR (int @var{filedes}, fd_set *@var{set}) | |
1550 | This macro removes @var{filedes} from the file descriptor set @var{set}. | |
d9997a45 UD |
1551 | |
1552 | The @var{filedes} parameter must not have side effects since it is | |
1553 | evaluated more than once. | |
28f540f4 RM |
1554 | @end deftypefn |
1555 | ||
1556 | @comment sys/types.h | |
1557 | @comment BSD | |
d9997a45 | 1558 | @deftypefn Macro int FD_ISSET (int @var{filedes}, const fd_set *@var{set}) |
28f540f4 | 1559 | This macro returns a nonzero value (true) if @var{filedes} is a member |
3081378b | 1560 | of the file descriptor set @var{set}, and zero (false) otherwise. |
d9997a45 UD |
1561 | |
1562 | The @var{filedes} parameter must not have side effects since it is | |
1563 | evaluated more than once. | |
28f540f4 RM |
1564 | @end deftypefn |
1565 | ||
1566 | Next, here is the description of the @code{select} function itself. | |
1567 | ||
1568 | @comment sys/types.h | |
1569 | @comment BSD | |
1570 | @deftypefun int select (int @var{nfds}, fd_set *@var{read-fds}, fd_set *@var{write-fds}, fd_set *@var{except-fds}, struct timeval *@var{timeout}) | |
1571 | The @code{select} function blocks the calling process until there is | |
1572 | activity on any of the specified sets of file descriptors, or until the | |
1573 | timeout period has expired. | |
1574 | ||
1575 | The file descriptors specified by the @var{read-fds} argument are | |
1576 | checked to see if they are ready for reading; the @var{write-fds} file | |
1577 | descriptors are checked to see if they are ready for writing; and the | |
1578 | @var{except-fds} file descriptors are checked for exceptional | |
1579 | conditions. You can pass a null pointer for any of these arguments if | |
1580 | you are not interested in checking for that kind of condition. | |
1581 | ||
76de2021 UD |
1582 | A file descriptor is considered ready for reading if a @code{read} |
1583 | call will not block. This usually includes the read offset being at | |
1584 | the end of the file or there is an error to report. A server socket | |
1585 | is considered ready for reading if there is a pending connection which | |
1586 | can be accepted with @code{accept}; @pxref{Accepting Connections}. A | |
1587 | client socket is ready for writing when its connection is fully | |
1588 | established; @pxref{Connecting}. | |
28f540f4 RM |
1589 | |
1590 | ``Exceptional conditions'' does not mean errors---errors are reported | |
1591 | immediately when an erroneous system call is executed, and do not | |
1592 | constitute a state of the descriptor. Rather, they include conditions | |
1593 | such as the presence of an urgent message on a socket. (@xref{Sockets}, | |
1594 | for information on urgent messages.) | |
1595 | ||
1596 | The @code{select} function checks only the first @var{nfds} file | |
1597 | descriptors. The usual thing is to pass @code{FD_SETSIZE} as the value | |
1598 | of this argument. | |
1599 | ||
1600 | The @var{timeout} specifies the maximum time to wait. If you pass a | |
1601 | null pointer for this argument, it means to block indefinitely until one | |
1602 | of the file descriptors is ready. Otherwise, you should provide the | |
1603 | time in @code{struct timeval} format; see @ref{High-Resolution | |
1604 | Calendar}. Specify zero as the time (a @code{struct timeval} containing | |
1605 | all zeros) if you want to find out which descriptors are ready without | |
1606 | waiting if none are ready. | |
1607 | ||
1608 | The normal return value from @code{select} is the total number of ready file | |
1609 | descriptors in all of the sets. Each of the argument sets is overwritten | |
1610 | with information about the descriptors that are ready for the corresponding | |
1611 | operation. Thus, to see if a particular descriptor @var{desc} has input, | |
1612 | use @code{FD_ISSET (@var{desc}, @var{read-fds})} after @code{select} returns. | |
1613 | ||
1614 | If @code{select} returns because the timeout period expires, it returns | |
1615 | a value of zero. | |
1616 | ||
1617 | Any signal will cause @code{select} to return immediately. So if your | |
1618 | program uses signals, you can't rely on @code{select} to keep waiting | |
1619 | for the full time specified. If you want to be sure of waiting for a | |
1620 | particular amount of time, you must check for @code{EINTR} and repeat | |
1621 | the @code{select} with a newly calculated timeout based on the current | |
1622 | time. See the example below. See also @ref{Interrupted Primitives}. | |
1623 | ||
1624 | If an error occurs, @code{select} returns @code{-1} and does not modify | |
2c6fe0bd | 1625 | the argument file descriptor sets. The following @code{errno} error |
28f540f4 RM |
1626 | conditions are defined for this function: |
1627 | ||
1628 | @table @code | |
1629 | @item EBADF | |
1630 | One of the file descriptor sets specified an invalid file descriptor. | |
1631 | ||
1632 | @item EINTR | |
1633 | The operation was interrupted by a signal. @xref{Interrupted Primitives}. | |
1634 | ||
1635 | @item EINVAL | |
1636 | The @var{timeout} argument is invalid; one of the components is negative | |
1637 | or too large. | |
1638 | @end table | |
1639 | @end deftypefun | |
1640 | ||
1641 | @strong{Portability Note:} The @code{select} function is a BSD Unix | |
1642 | feature. | |
1643 | ||
1644 | Here is an example showing how you can use @code{select} to establish a | |
1645 | timeout period for reading from a file descriptor. The @code{input_timeout} | |
1646 | function blocks the calling process until input is available on the | |
1647 | file descriptor, or until the timeout period expires. | |
1648 | ||
1649 | @smallexample | |
1650 | @include select.c.texi | |
1651 | @end smallexample | |
1652 | ||
1653 | There is another example showing the use of @code{select} to multiplex | |
1654 | input from multiple sockets in @ref{Server Example}. | |
1655 | ||
1656 | ||
dfd2257a UD |
1657 | @node Synchronizing I/O |
1658 | @section Synchronizing I/O operations | |
1659 | ||
1660 | @cindex synchronizing | |
19e4c7dd | 1661 | In most modern operating systems, the normal I/O operations are not |
dfd2257a | 1662 | executed synchronously. I.e., even if a @code{write} system call |
19e4c7dd | 1663 | returns, this does not mean the data is actually written to the media, |
dfd2257a UD |
1664 | e.g., the disk. |
1665 | ||
19e4c7dd | 1666 | In situations where synchronization points are necessary, you can use |
04b9968b | 1667 | special functions which ensure that all operations finish before |
dfd2257a UD |
1668 | they return. |
1669 | ||
1670 | @comment unistd.h | |
1671 | @comment X/Open | |
1672 | @deftypefun int sync (void) | |
1673 | A call to this function will not return as long as there is data which | |
04b9968b | 1674 | has not been written to the device. All dirty buffers in the kernel will |
dfd2257a UD |
1675 | be written and so an overall consistent system can be achieved (if no |
1676 | other process in parallel writes data). | |
1677 | ||
1678 | A prototype for @code{sync} can be found in @file{unistd.h}. | |
1679 | ||
1680 | The return value is zero to indicate no error. | |
1681 | @end deftypefun | |
1682 | ||
04b9968b UD |
1683 | Programs more often want to ensure that data written to a given file is |
1684 | committed, rather than all data in the system. For this, @code{sync} is overkill. | |
1685 | ||
dfd2257a UD |
1686 | |
1687 | @comment unistd.h | |
1688 | @comment POSIX | |
1689 | @deftypefun int fsync (int @var{fildes}) | |
19e4c7dd AJ |
1690 | The @code{fsync} function can be used to make sure all data associated with |
1691 | the open file @var{fildes} is written to the device associated with the | |
dfd2257a UD |
1692 | descriptor. The function call does not return unless all actions have |
1693 | finished. | |
1694 | ||
1695 | A prototype for @code{fsync} can be found in @file{unistd.h}. | |
1696 | ||
04b9968b | 1697 | This function is a cancellation point in multi-threaded programs. This |
dfd2257a UD |
1698 | is a problem if the thread allocates some resources (like memory, file |
1699 | descriptors, semaphores or whatever) at the time @code{fsync} is | |
19e4c7dd | 1700 | called. If the thread gets canceled these resources stay allocated |
04b9968b UD |
1701 | until the program ends. To avoid this, calls to @code{fsync} should be |
1702 | protected using cancellation handlers. | |
dfd2257a UD |
1703 | @c ref pthread_cleanup_push / pthread_cleanup_pop |
1704 | ||
49c091e5 | 1705 | The return value of the function is zero if no error occurred. Otherwise |
dfd2257a UD |
1706 | it is @math{-1} and the global variable @var{errno} is set to the |
1707 | following values: | |
1708 | @table @code | |
1709 | @item EBADF | |
1710 | The descriptor @var{fildes} is not valid. | |
1711 | ||
1712 | @item EINVAL | |
1713 | No synchronization is possible since the system does not implement this. | |
1714 | @end table | |
1715 | @end deftypefun | |
1716 | ||
1717 | Sometimes it is not even necessary to write all data associated with a | |
1718 | file descriptor. E.g., in database files which do not change in size it | |
1719 | is enough to write all the file content data to the device. | |
19e4c7dd | 1720 | Meta-information, like the modification time etc., are not that important |
dfd2257a UD |
1721 | and leaving such information uncommitted does not prevent a successful |
1722 | recovering of the file in case of a problem. | |
1723 | ||
1724 | @comment unistd.h | |
1725 | @comment POSIX | |
1726 | @deftypefun int fdatasync (int @var{fildes}) | |
04b9968b | 1727 | When a call to the @code{fdatasync} function returns, it is ensured |
dfd2257a | 1728 | that all of the file data is written to the device. For all pending I/O |
04b9968b | 1729 | operations, the parts guaranteeing data integrity finished. |
dfd2257a UD |
1730 | |
1731 | Not all systems implement the @code{fdatasync} operation. On systems | |
1732 | missing this functionality @code{fdatasync} is emulated by a call to | |
1733 | @code{fsync} since the performed actions are a superset of those | |
19e4c7dd | 1734 | required by @code{fdatasync}. |
dfd2257a UD |
1735 | |
1736 | The prototype for @code{fdatasync} is in @file{unistd.h}. | |
1737 | ||
49c091e5 | 1738 | The return value of the function is zero if no error occurred. Otherwise |
dfd2257a UD |
1739 | it is @math{-1} and the global variable @var{errno} is set to the |
1740 | following values: | |
1741 | @table @code | |
1742 | @item EBADF | |
1743 | The descriptor @var{fildes} is not valid. | |
1744 | ||
1745 | @item EINVAL | |
1746 | No synchronization is possible since the system does not implement this. | |
1747 | @end table | |
1748 | @end deftypefun | |
1749 | ||
1750 | ||
b07d03e0 UD |
1751 | @node Asynchronous I/O |
1752 | @section Perform I/O Operations in Parallel | |
1753 | ||
1754 | The POSIX.1b standard defines a new set of I/O operations which can | |
04b9968b | 1755 | significantly reduce the time an application spends waiting at I/O. The |
b07d03e0 | 1756 | new functions allow a program to initiate one or more I/O operations and |
04b9968b UD |
1757 | then immediately resume normal work while the I/O operations are |
1758 | executed in parallel. This functionality is available if the | |
a3a4a74e | 1759 | @file{unistd.h} file defines the symbol @code{_POSIX_ASYNCHRONOUS_IO}. |
b07d03e0 UD |
1760 | |
1761 | These functions are part of the library with realtime functions named | |
1762 | @file{librt}. They are not actually part of the @file{libc} binary. | |
1763 | The implementation of these functions can be done using support in the | |
c756c71c UD |
1764 | kernel (if available) or using an implementation based on threads at |
1765 | userlevel. In the latter case it might be necessary to link applications | |
fed8f7f7 | 1766 | with the thread library @file{libpthread} in addition to @file{librt}. |
b07d03e0 | 1767 | |
c756c71c | 1768 | All AIO operations operate on files which were opened previously. There |
04b9968b | 1769 | might be arbitrarily many operations running for one file. The |
b07d03e0 UD |
1770 | asynchronous I/O operations are controlled using a data structure named |
1771 | @code{struct aiocb} (@dfn{AIO control block}). It is defined in | |
1772 | @file{aio.h} as follows. | |
1773 | ||
1774 | @comment aio.h | |
1775 | @comment POSIX.1b | |
1776 | @deftp {Data Type} {struct aiocb} | |
1777 | The POSIX.1b standard mandates that the @code{struct aiocb} structure | |
1778 | contains at least the members described in the following table. There | |
04b9968b | 1779 | might be more elements which are used by the implementation, but |
19e4c7dd | 1780 | depending upon these elements is not portable and is highly deprecated. |
b07d03e0 UD |
1781 | |
1782 | @table @code | |
1783 | @item int aio_fildes | |
19e4c7dd AJ |
1784 | This element specifies the file descriptor to be used for the |
1785 | operation. It must be a legal descriptor, otherwise the operation will | |
1786 | fail. | |
b07d03e0 UD |
1787 | |
1788 | The device on which the file is opened must allow the seek operation. | |
1789 | I.e., it is not possible to use any of the AIO operations on devices | |
1790 | like terminals where an @code{lseek} call would lead to an error. | |
1791 | ||
1792 | @item off_t aio_offset | |
19e4c7dd | 1793 | This element specifies the offset in the file at which the operation (input |
fed8f7f7 | 1794 | or output) is performed. Since the operations are carried out in arbitrary |
b07d03e0 UD |
1795 | order and more than one operation for one file descriptor can be |
1796 | started, one cannot expect a current read/write position of the file | |
1797 | descriptor. | |
1798 | ||
1799 | @item volatile void *aio_buf | |
1800 | This is a pointer to the buffer with the data to be written or the place | |
c756c71c | 1801 | where the read data is stored. |
b07d03e0 UD |
1802 | |
1803 | @item size_t aio_nbytes | |
1804 | This element specifies the length of the buffer pointed to by @code{aio_buf}. | |
1805 | ||
1806 | @item int aio_reqprio | |
c756c71c | 1807 | If the platform has defined @code{_POSIX_PRIORITIZED_IO} and |
19e4c7dd | 1808 | @code{_POSIX_PRIORITY_SCHEDULING}, the AIO requests are |
b07d03e0 UD |
1809 | processed based on the current scheduling priority. The |
1810 | @code{aio_reqprio} element can then be used to lower the priority of the | |
1811 | AIO operation. | |
1812 | ||
1813 | @item struct sigevent aio_sigevent | |
1814 | This element specifies how the calling process is notified once the | |
fed8f7f7 | 1815 | operation terminates. If the @code{sigev_notify} element is |
19e4c7dd AJ |
1816 | @code{SIGEV_NONE}, no notification is sent. If it is @code{SIGEV_SIGNAL}, |
1817 | the signal determined by @code{sigev_signo} is sent. Otherwise, | |
1818 | @code{sigev_notify} must be @code{SIGEV_THREAD}. In this case, a thread | |
c756c71c | 1819 | is created which starts executing the function pointed to by |
b07d03e0 UD |
1820 | @code{sigev_notify_function}. |
1821 | ||
1822 | @item int aio_lio_opcode | |
1823 | This element is only used by the @code{lio_listio} and | |
04b9968b UD |
1824 | @code{lio_listio64} functions. Since these functions allow an |
1825 | arbitrary number of operations to start at once, and each operation can be | |
1826 | input or output (or nothing), the information must be stored in the | |
b07d03e0 UD |
1827 | control block. The possible values are: |
1828 | ||
1829 | @vtable @code | |
1830 | @item LIO_READ | |
1831 | Start a read operation. Read from the file at position | |
1832 | @code{aio_offset} and store the next @code{aio_nbytes} bytes in the | |
1833 | buffer pointed to by @code{aio_buf}. | |
1834 | ||
1835 | @item LIO_WRITE | |
1836 | Start a write operation. Write @code{aio_nbytes} bytes starting at | |
1837 | @code{aio_buf} into the file starting at position @code{aio_offset}. | |
1838 | ||
1839 | @item LIO_NOP | |
1840 | Do nothing for this control block. This value is useful sometimes when | |
1841 | an array of @code{struct aiocb} values contains holes, i.e., some of the | |
fed8f7f7 | 1842 | values must not be handled although the whole array is presented to the |
b07d03e0 UD |
1843 | @code{lio_listio} function. |
1844 | @end vtable | |
1845 | @end table | |
a3a4a74e | 1846 | |
fed8f7f7 | 1847 | When the sources are compiled using @code{_FILE_OFFSET_BITS == 64} on a |
19e4c7dd | 1848 | 32 bit machine, this type is in fact @code{struct aiocb64}, since the LFS |
a3a4a74e UD |
1849 | interface transparently replaces the @code{struct aiocb} definition. |
1850 | @end deftp | |
1851 | ||
19e4c7dd | 1852 | For use with the AIO functions defined in the LFS, there is a similar type |
a3a4a74e | 1853 | defined which replaces the types of the appropriate members with larger |
04b9968b | 1854 | types but otherwise is equivalent to @code{struct aiocb}. Particularly, |
a3a4a74e UD |
1855 | all member names are the same. |
1856 | ||
1857 | @comment aio.h | |
1858 | @comment POSIX.1b | |
1859 | @deftp {Data Type} {struct aiocb64} | |
1860 | @table @code | |
1861 | @item int aio_fildes | |
1862 | This element specifies the file descriptor which is used for the | |
1863 | operation. It must be a legal descriptor since otherwise the operation | |
1864 | fails for obvious reasons. | |
1865 | ||
1866 | The device on which the file is opened must allow the seek operation. | |
1867 | I.e., it is not possible to use any of the AIO operations on devices | |
1868 | like terminals where an @code{lseek} call would lead to an error. | |
1869 | ||
1870 | @item off64_t aio_offset | |
04b9968b | 1871 | This element specifies at which offset in the file the operation (input |
a3a4a74e UD |
1872 | or output) is performed. Since the operation are carried in arbitrary |
1873 | order and more than one operation for one file descriptor can be | |
1874 | started, one cannot expect a current read/write position of the file | |
1875 | descriptor. | |
1876 | ||
1877 | @item volatile void *aio_buf | |
1878 | This is a pointer to the buffer with the data to be written or the place | |
19e4c7dd | 1879 | where the read data is stored. |
a3a4a74e UD |
1880 | |
1881 | @item size_t aio_nbytes | |
1882 | This element specifies the length of the buffer pointed to by @code{aio_buf}. | |
1883 | ||
1884 | @item int aio_reqprio | |
1885 | If for the platform @code{_POSIX_PRIORITIZED_IO} and | |
04b9968b | 1886 | @code{_POSIX_PRIORITY_SCHEDULING} are defined the AIO requests are |
a3a4a74e UD |
1887 | processed based on the current scheduling priority. The |
1888 | @code{aio_reqprio} element can then be used to lower the priority of the | |
1889 | AIO operation. | |
1890 | ||
1891 | @item struct sigevent aio_sigevent | |
1892 | This element specifies how the calling process is notified once the | |
19e4c7dd AJ |
1893 | operation terminates. If the @code{sigev_notify}, element is |
1894 | @code{SIGEV_NONE} no notification is sent. If it is @code{SIGEV_SIGNAL}, | |
1895 | the signal determined by @code{sigev_signo} is sent. Otherwise, | |
a3a4a74e | 1896 | @code{sigev_notify} must be @code{SIGEV_THREAD} in which case a thread |
04b9968b | 1897 | which starts executing the function pointed to by |
a3a4a74e UD |
1898 | @code{sigev_notify_function}. |
1899 | ||
1900 | @item int aio_lio_opcode | |
1901 | This element is only used by the @code{lio_listio} and | |
04b9968b UD |
1902 | @code{[lio_listio64} functions. Since these functions allow an |
1903 | arbitrary number of operations to start at once, and since each operation can be | |
1904 | input or output (or nothing), the information must be stored in the | |
a3a4a74e UD |
1905 | control block. See the description of @code{struct aiocb} for a description |
1906 | of the possible values. | |
1907 | @end table | |
1908 | ||
1909 | When the sources are compiled using @code{_FILE_OFFSET_BITS == 64} on a | |
19e4c7dd AJ |
1910 | 32 bit machine, this type is available under the name @code{struct |
1911 | aiocb64}, since the LFS transparently replaces the old interface. | |
b07d03e0 UD |
1912 | @end deftp |
1913 | ||
1914 | @menu | |
a3a4a74e UD |
1915 | * Asynchronous Reads/Writes:: Asynchronous Read and Write Operations. |
1916 | * Status of AIO Operations:: Getting the Status of AIO Operations. | |
1917 | * Synchronizing AIO Operations:: Getting into a consistent state. | |
04b9968b | 1918 | * Cancel AIO Operations:: Cancellation of AIO Operations. |
a3a4a74e | 1919 | * Configuration of AIO:: How to optimize the AIO implementation. |
b07d03e0 UD |
1920 | @end menu |
1921 | ||
a3a4a74e UD |
1922 | @node Asynchronous Reads/Writes |
1923 | @subsection Asynchronous Read and Write Operations | |
b07d03e0 UD |
1924 | |
1925 | @comment aio.h | |
1926 | @comment POSIX.1b | |
1927 | @deftypefun int aio_read (struct aiocb *@var{aiocbp}) | |
04b9968b UD |
1928 | This function initiates an asynchronous read operation. It |
1929 | immediately returns after the operation was enqueued or when an | |
fed8f7f7 | 1930 | error was encountered. |
b07d03e0 | 1931 | |
a3a4a74e | 1932 | The first @code{aiocbp->aio_nbytes} bytes of the file for which |
c756c71c UD |
1933 | @code{aiocbp->aio_fildes} is a descriptor are written to the buffer |
1934 | starting at @code{aiocbp->aio_buf}. Reading starts at the absolute | |
1935 | position @code{aiocbp->aio_offset} in the file. | |
b07d03e0 UD |
1936 | |
1937 | If prioritized I/O is supported by the platform the | |
1938 | @code{aiocbp->aio_reqprio} value is used to adjust the priority before | |
1939 | the request is actually enqueued. | |
1940 | ||
1941 | The calling process is notified about the termination of the read | |
1942 | request according to the @code{aiocbp->aio_sigevent} value. | |
1943 | ||
04b9968b | 1944 | When @code{aio_read} returns, the return value is zero if no error |
b07d03e0 | 1945 | occurred that can be found before the process is enqueued. If such an |
04b9968b UD |
1946 | early error is found, the function returns @math{-1} and sets |
1947 | @code{errno} to one of the following values: | |
b07d03e0 UD |
1948 | |
1949 | @table @code | |
1950 | @item EAGAIN | |
1951 | The request was not enqueued due to (temporarily) exceeded resource | |
1952 | limitations. | |
1953 | @item ENOSYS | |
1954 | The @code{aio_read} function is not implemented. | |
1955 | @item EBADF | |
1956 | The @code{aiocbp->aio_fildes} descriptor is not valid. This condition | |
04b9968b | 1957 | need not be recognized before enqueueing the request and so this error |
fed8f7f7 | 1958 | might also be signaled asynchronously. |
b07d03e0 UD |
1959 | @item EINVAL |
1960 | The @code{aiocbp->aio_offset} or @code{aiocbp->aio_reqpiro} value is | |
1961 | invalid. This condition need not be recognized before enqueueing the | |
49c091e5 | 1962 | request and so this error might also be signaled asynchronously. |
b07d03e0 UD |
1963 | @end table |
1964 | ||
04b9968b UD |
1965 | If @code{aio_read} returns zero, the current status of the request |
1966 | can be queried using @code{aio_error} and @code{aio_return} functions. | |
1967 | As long as the value returned by @code{aio_error} is @code{EINPROGRESS} | |
1968 | the operation has not yet completed. If @code{aio_error} returns zero, | |
78759725 UD |
1969 | the operation successfully terminated, otherwise the value is to be |
1970 | interpreted as an error code. If the function terminated, the result of | |
1971 | the operation can be obtained using a call to @code{aio_return}. The | |
1972 | returned value is the same as an equivalent call to @code{read} would | |
04b9968b | 1973 | have returned. Possible error codes returned by @code{aio_error} are: |
b07d03e0 UD |
1974 | |
1975 | @table @code | |
1976 | @item EBADF | |
1977 | The @code{aiocbp->aio_fildes} descriptor is not valid. | |
1978 | @item ECANCELED | |
19e4c7dd | 1979 | The operation was canceled before the operation was finished |
b07d03e0 UD |
1980 | (@pxref{Cancel AIO Operations}) |
1981 | @item EINVAL | |
1982 | The @code{aiocbp->aio_offset} value is invalid. | |
1983 | @end table | |
a3a4a74e UD |
1984 | |
1985 | When the sources are compiled with @code{_FILE_OFFSET_BITS == 64} this | |
1986 | function is in fact @code{aio_read64} since the LFS interface transparently | |
1987 | replaces the normal implementation. | |
b07d03e0 UD |
1988 | @end deftypefun |
1989 | ||
1990 | @comment aio.h | |
a3a4a74e | 1991 | @comment Unix98 |
b07d03e0 UD |
1992 | @deftypefun int aio_read64 (struct aiocb *@var{aiocbp}) |
1993 | This function is similar to the @code{aio_read} function. The only | |
19e4c7dd AJ |
1994 | difference is that on @w{32 bit} machines, the file descriptor should |
1995 | be opened in the large file mode. Internally, @code{aio_read64} uses | |
a3a4a74e UD |
1996 | functionality equivalent to @code{lseek64} (@pxref{File Position |
1997 | Primitive}) to position the file descriptor correctly for the reading, | |
fed8f7f7 | 1998 | as opposed to @code{lseek} functionality used in @code{aio_read}. |
a3a4a74e | 1999 | |
19e4c7dd | 2000 | When the sources are compiled with @code{_FILE_OFFSET_BITS == 64}, this |
a3a4a74e | 2001 | function is available under the name @code{aio_read} and so transparently |
04b9968b | 2002 | replaces the interface for small files on 32 bit machines. |
b07d03e0 UD |
2003 | @end deftypefun |
2004 | ||
19e4c7dd | 2005 | To write data asynchronously to a file, there exists an equivalent pair |
a3a4a74e UD |
2006 | of functions with a very similar interface. |
2007 | ||
2008 | @comment aio.h | |
2009 | @comment POSIX.1b | |
2010 | @deftypefun int aio_write (struct aiocb *@var{aiocbp}) | |
2011 | This function initiates an asynchronous write operation. The function | |
2012 | call immediately returns after the operation was enqueued or if before | |
fed8f7f7 | 2013 | this happens an error was encountered. |
a3a4a74e UD |
2014 | |
2015 | The first @code{aiocbp->aio_nbytes} bytes from the buffer starting at | |
2016 | @code{aiocbp->aio_buf} are written to the file for which | |
2017 | @code{aiocbp->aio_fildes} is an descriptor, starting at the absolute | |
2018 | position @code{aiocbp->aio_offset} in the file. | |
2019 | ||
19e4c7dd | 2020 | If prioritized I/O is supported by the platform, the |
a3a4a74e UD |
2021 | @code{aiocbp->aio_reqprio} value is used to adjust the priority before |
2022 | the request is actually enqueued. | |
2023 | ||
2024 | The calling process is notified about the termination of the read | |
2025 | request according to the @code{aiocbp->aio_sigevent} value. | |
2026 | ||
19e4c7dd | 2027 | When @code{aio_write} returns, the return value is zero if no error |
a3a4a74e UD |
2028 | occurred that can be found before the process is enqueued. If such an |
2029 | early error is found the function returns @math{-1} and sets | |
2030 | @code{errno} to one of the following values. | |
2031 | ||
2032 | @table @code | |
2033 | @item EAGAIN | |
2034 | The request was not enqueued due to (temporarily) exceeded resource | |
2035 | limitations. | |
2036 | @item ENOSYS | |
2037 | The @code{aio_write} function is not implemented. | |
2038 | @item EBADF | |
2039 | The @code{aiocbp->aio_fildes} descriptor is not valid. This condition | |
19e4c7dd | 2040 | may not be recognized before enqueueing the request, and so this error |
fed8f7f7 | 2041 | might also be signaled asynchronously. |
a3a4a74e | 2042 | @item EINVAL |
19e4c7dd AJ |
2043 | The @code{aiocbp->aio_offset} or @code{aiocbp->aio_reqprio} value is |
2044 | invalid. This condition may not be recognized before enqueueing the | |
fed8f7f7 | 2045 | request and so this error might also be signaled asynchronously. |
a3a4a74e UD |
2046 | @end table |
2047 | ||
19e4c7dd | 2048 | In the case @code{aio_write} returns zero, the current status of the |
a3a4a74e | 2049 | request can be queried using @code{aio_error} and @code{aio_return} |
c756c71c | 2050 | functions. As long as the value returned by @code{aio_error} is |
a3a4a74e | 2051 | @code{EINPROGRESS} the operation has not yet completed. If |
19e4c7dd | 2052 | @code{aio_error} returns zero, the operation successfully terminated, |
a3a4a74e | 2053 | otherwise the value is to be interpreted as an error code. If the |
19e4c7dd | 2054 | function terminated, the result of the operation can be get using a call |
a3a4a74e | 2055 | to @code{aio_return}. The returned value is the same as an equivalent |
19e4c7dd | 2056 | call to @code{read} would have returned. Possible error codes returned |
a3a4a74e UD |
2057 | by @code{aio_error} are: |
2058 | ||
2059 | @table @code | |
2060 | @item EBADF | |
2061 | The @code{aiocbp->aio_fildes} descriptor is not valid. | |
2062 | @item ECANCELED | |
19e4c7dd | 2063 | The operation was canceled before the operation was finished. |
a3a4a74e UD |
2064 | (@pxref{Cancel AIO Operations}) |
2065 | @item EINVAL | |
2066 | The @code{aiocbp->aio_offset} value is invalid. | |
2067 | @end table | |
2068 | ||
19e4c7dd | 2069 | When the sources are compiled with @code{_FILE_OFFSET_BITS == 64}, this |
a3a4a74e UD |
2070 | function is in fact @code{aio_write64} since the LFS interface transparently |
2071 | replaces the normal implementation. | |
2072 | @end deftypefun | |
2073 | ||
2074 | @comment aio.h | |
2075 | @comment Unix98 | |
2076 | @deftypefun int aio_write64 (struct aiocb *@var{aiocbp}) | |
2077 | This function is similar to the @code{aio_write} function. The only | |
04b9968b | 2078 | difference is that on @w{32 bit} machines the file descriptor should |
a3a4a74e UD |
2079 | be opened in the large file mode. Internally @code{aio_write64} uses |
2080 | functionality equivalent to @code{lseek64} (@pxref{File Position | |
2081 | Primitive}) to position the file descriptor correctly for the writing, | |
fed8f7f7 | 2082 | as opposed to @code{lseek} functionality used in @code{aio_write}. |
a3a4a74e | 2083 | |
19e4c7dd | 2084 | When the sources are compiled with @code{_FILE_OFFSET_BITS == 64}, this |
a3a4a74e | 2085 | function is available under the name @code{aio_write} and so transparently |
04b9968b | 2086 | replaces the interface for small files on 32 bit machines. |
a3a4a74e UD |
2087 | @end deftypefun |
2088 | ||
19e4c7dd AJ |
2089 | Besides these functions with the more or less traditional interface, |
2090 | POSIX.1b also defines a function which can initiate more than one | |
2091 | operation at a time, and which can handle freely mixed read and write | |
2092 | operations. It is therefore similar to a combination of @code{readv} and | |
a3a4a74e UD |
2093 | @code{writev}. |
2094 | ||
2095 | @comment aio.h | |
2096 | @comment POSIX.1b | |
2097 | @deftypefun int lio_listio (int @var{mode}, struct aiocb *const @var{list}[], int @var{nent}, struct sigevent *@var{sig}) | |
2098 | The @code{lio_listio} function can be used to enqueue an arbitrary | |
2099 | number of read and write requests at one time. The requests can all be | |
2100 | meant for the same file, all for different files or every solution in | |
2101 | between. | |
2102 | ||
2103 | @code{lio_listio} gets the @var{nent} requests from the array pointed to | |
19e4c7dd | 2104 | by @var{list}. The operation to be performed is determined by the |
a3a4a74e | 2105 | @code{aio_lio_opcode} member in each element of @var{list}. If this |
19e4c7dd | 2106 | field is @code{LIO_READ} a read operation is enqueued, similar to a call |
a3a4a74e UD |
2107 | of @code{aio_read} for this element of the array (except that the way |
2108 | the termination is signalled is different, as we will see below). If | |
19e4c7dd | 2109 | the @code{aio_lio_opcode} member is @code{LIO_WRITE} a write operation |
a3a4a74e UD |
2110 | is enqueued. Otherwise the @code{aio_lio_opcode} must be @code{LIO_NOP} |
2111 | in which case this element of @var{list} is simply ignored. This | |
2112 | ``operation'' is useful in situations where one has a fixed array of | |
2113 | @code{struct aiocb} elements from which only a few need to be handled at | |
2114 | a time. Another situation is where the @code{lio_listio} call was | |
19e4c7dd | 2115 | canceled before all requests are processed (@pxref{Cancel AIO |
a3a4a74e UD |
2116 | Operations}) and the remaining requests have to be reissued. |
2117 | ||
fed8f7f7 | 2118 | The other members of each element of the array pointed to by |
a3a4a74e UD |
2119 | @code{list} must have values suitable for the operation as described in |
2120 | the documentation for @code{aio_read} and @code{aio_write} above. | |
2121 | ||
2122 | The @var{mode} argument determines how @code{lio_listio} behaves after | |
2123 | having enqueued all the requests. If @var{mode} is @code{LIO_WAIT} it | |
2124 | waits until all requests terminated. Otherwise @var{mode} must be | |
fed8f7f7 | 2125 | @code{LIO_NOWAIT} and in this case the function returns immediately after |
a3a4a74e UD |
2126 | having enqueued all the requests. In this case the caller gets a |
2127 | notification of the termination of all requests according to the | |
2128 | @var{sig} parameter. If @var{sig} is @code{NULL} no notification is | |
2129 | send. Otherwise a signal is sent or a thread is started, just as | |
2130 | described in the description for @code{aio_read} or @code{aio_write}. | |
2131 | ||
19e4c7dd | 2132 | If @var{mode} is @code{LIO_WAIT}, the return value of @code{lio_listio} |
a3a4a74e UD |
2133 | is @math{0} when all requests completed successfully. Otherwise the |
2134 | function return @math{-1} and @code{errno} is set accordingly. To find | |
2135 | out which request or requests failed one has to use the @code{aio_error} | |
2136 | function on all the elements of the array @var{list}. | |
2137 | ||
19e4c7dd | 2138 | In case @var{mode} is @code{LIO_NOWAIT}, the function returns @math{0} if |
a3a4a74e UD |
2139 | all requests were enqueued correctly. The current state of the requests |
2140 | can be found using @code{aio_error} and @code{aio_return} as described | |
19e4c7dd | 2141 | above. If @code{lio_listio} returns @math{-1} in this mode, the |
a3a4a74e | 2142 | global variable @code{errno} is set accordingly. If a request did not |
19e4c7dd AJ |
2143 | yet terminate, a call to @code{aio_error} returns @code{EINPROGRESS}. If |
2144 | the value is different, the request is finished and the error value (or | |
a3a4a74e UD |
2145 | @math{0}) is returned and the result of the operation can be retrieved |
2146 | using @code{aio_return}. | |
2147 | ||
2148 | Possible values for @code{errno} are: | |
2149 | ||
2150 | @table @code | |
2151 | @item EAGAIN | |
19e4c7dd | 2152 | The resources necessary to queue all the requests are not available at |
a3a4a74e | 2153 | the moment. The error status for each element of @var{list} must be |
19e4c7dd | 2154 | checked to determine which request failed. |
a3a4a74e | 2155 | |
fed8f7f7 | 2156 | Another reason could be that the system wide limit of AIO requests is |
a7a93d50 | 2157 | exceeded. This cannot be the case for the implementation on @gnusystems{} |
a3a4a74e UD |
2158 | since no arbitrary limits exist. |
2159 | @item EINVAL | |
2160 | The @var{mode} parameter is invalid or @var{nent} is larger than | |
2161 | @code{AIO_LISTIO_MAX}. | |
2162 | @item EIO | |
2163 | One or more of the request's I/O operations failed. The error status of | |
19e4c7dd | 2164 | each request should be checked to determine which one failed. |
a3a4a74e UD |
2165 | @item ENOSYS |
2166 | The @code{lio_listio} function is not supported. | |
2167 | @end table | |
2168 | ||
2169 | If the @var{mode} parameter is @code{LIO_NOWAIT} and the caller cancels | |
19e4c7dd | 2170 | a request, the error status for this request returned by |
a3a4a74e UD |
2171 | @code{aio_error} is @code{ECANCELED}. |
2172 | ||
19e4c7dd | 2173 | When the sources are compiled with @code{_FILE_OFFSET_BITS == 64}, this |
a3a4a74e UD |
2174 | function is in fact @code{lio_listio64} since the LFS interface |
2175 | transparently replaces the normal implementation. | |
2176 | @end deftypefun | |
2177 | ||
2178 | @comment aio.h | |
2179 | @comment Unix98 | |
2180 | @deftypefun int lio_listio64 (int @var{mode}, struct aiocb *const @var{list}, int @var{nent}, struct sigevent *@var{sig}) | |
19e4c7dd AJ |
2181 | This function is similar to the @code{lio_listio} function. The only |
2182 | difference is that on @w{32 bit} machines, the file descriptor should | |
2183 | be opened in the large file mode. Internally, @code{lio_listio64} uses | |
a3a4a74e UD |
2184 | functionality equivalent to @code{lseek64} (@pxref{File Position |
2185 | Primitive}) to position the file descriptor correctly for the reading or | |
fed8f7f7 | 2186 | writing, as opposed to @code{lseek} functionality used in |
a3a4a74e UD |
2187 | @code{lio_listio}. |
2188 | ||
19e4c7dd | 2189 | When the sources are compiled with @code{_FILE_OFFSET_BITS == 64}, this |
a3a4a74e | 2190 | function is available under the name @code{lio_listio} and so |
04b9968b | 2191 | transparently replaces the interface for small files on 32 bit |
a3a4a74e UD |
2192 | machines. |
2193 | @end deftypefun | |
2194 | ||
2195 | @node Status of AIO Operations | |
2196 | @subsection Getting the Status of AIO Operations | |
2197 | ||
fed8f7f7 | 2198 | As already described in the documentation of the functions in the last |
04b9968b UD |
2199 | section, it must be possible to get information about the status of an I/O |
2200 | request. When the operation is performed truly asynchronously (as with | |
19e4c7dd AJ |
2201 | @code{aio_read} and @code{aio_write} and with @code{lio_listio} when the |
2202 | mode is @code{LIO_NOWAIT}), one sometimes needs to know whether a | |
2203 | specific request already terminated and if so, what the result was. | |
04b9968b | 2204 | The following two functions allow you to get this kind of information. |
a3a4a74e UD |
2205 | |
2206 | @comment aio.h | |
2207 | @comment POSIX.1b | |
2208 | @deftypefun int aio_error (const struct aiocb *@var{aiocbp}) | |
2209 | This function determines the error state of the request described by the | |
fed8f7f7 | 2210 | @code{struct aiocb} variable pointed to by @var{aiocbp}. If the |
a3a4a74e UD |
2211 | request has not yet terminated the value returned is always |
2212 | @code{EINPROGRESS}. Once the request has terminated the value | |
2213 | @code{aio_error} returns is either @math{0} if the request completed | |
fed8f7f7 | 2214 | successfully or it returns the value which would be stored in the |
a3a4a74e UD |
2215 | @code{errno} variable if the request would have been done using |
2216 | @code{read}, @code{write}, or @code{fsync}. | |
2217 | ||
2218 | The function can return @code{ENOSYS} if it is not implemented. It | |
2219 | could also return @code{EINVAL} if the @var{aiocbp} parameter does not | |
2220 | refer to an asynchronous operation whose return status is not yet known. | |
2221 | ||
2222 | When the sources are compiled with @code{_FILE_OFFSET_BITS == 64} this | |
2223 | function is in fact @code{aio_error64} since the LFS interface | |
2224 | transparently replaces the normal implementation. | |
2225 | @end deftypefun | |
2226 | ||
2227 | @comment aio.h | |
2228 | @comment Unix98 | |
2229 | @deftypefun int aio_error64 (const struct aiocb64 *@var{aiocbp}) | |
2230 | This function is similar to @code{aio_error} with the only difference | |
2231 | that the argument is a reference to a variable of type @code{struct | |
2232 | aiocb64}. | |
2233 | ||
2234 | When the sources are compiled with @code{_FILE_OFFSET_BITS == 64} this | |
2235 | function is available under the name @code{aio_error} and so | |
04b9968b | 2236 | transparently replaces the interface for small files on 32 bit |
a3a4a74e UD |
2237 | machines. |
2238 | @end deftypefun | |
2239 | ||
2240 | @comment aio.h | |
2241 | @comment POSIX.1b | |
2242 | @deftypefun ssize_t aio_return (const struct aiocb *@var{aiocbp}) | |
2243 | This function can be used to retrieve the return status of the operation | |
2244 | carried out by the request described in the variable pointed to by | |
2245 | @var{aiocbp}. As long as the error status of this request as returned | |
2246 | by @code{aio_error} is @code{EINPROGRESS} the return of this function is | |
2247 | undefined. | |
2248 | ||
fed8f7f7 UD |
2249 | Once the request is finished this function can be used exactly once to |
2250 | retrieve the return value. Following calls might lead to undefined | |
19e4c7dd | 2251 | behavior. The return value itself is the value which would have been |
a3a4a74e UD |
2252 | returned by the @code{read}, @code{write}, or @code{fsync} call. |
2253 | ||
2254 | The function can return @code{ENOSYS} if it is not implemented. It | |
2255 | could also return @code{EINVAL} if the @var{aiocbp} parameter does not | |
2256 | refer to an asynchronous operation whose return status is not yet known. | |
2257 | ||
2258 | When the sources are compiled with @code{_FILE_OFFSET_BITS == 64} this | |
2259 | function is in fact @code{aio_return64} since the LFS interface | |
2260 | transparently replaces the normal implementation. | |
2261 | @end deftypefun | |
2262 | ||
2263 | @comment aio.h | |
2264 | @comment Unix98 | |
2265 | @deftypefun int aio_return64 (const struct aiocb64 *@var{aiocbp}) | |
2266 | This function is similar to @code{aio_return} with the only difference | |
2267 | that the argument is a reference to a variable of type @code{struct | |
2268 | aiocb64}. | |
2269 | ||
2270 | When the sources are compiled with @code{_FILE_OFFSET_BITS == 64} this | |
2271 | function is available under the name @code{aio_return} and so | |
04b9968b | 2272 | transparently replaces the interface for small files on 32 bit |
a3a4a74e UD |
2273 | machines. |
2274 | @end deftypefun | |
2275 | ||
2276 | @node Synchronizing AIO Operations | |
2277 | @subsection Getting into a Consistent State | |
2278 | ||
2279 | When dealing with asynchronous operations it is sometimes necessary to | |
fed8f7f7 | 2280 | get into a consistent state. This would mean for AIO that one wants to |
a3a4a74e UD |
2281 | know whether a certain request or a group of request were processed. |
2282 | This could be done by waiting for the notification sent by the system | |
04b9968b | 2283 | after the operation terminated, but this sometimes would mean wasting |
a3a4a74e UD |
2284 | resources (mainly computation time). Instead POSIX.1b defines two |
2285 | functions which will help with most kinds of consistency. | |
2286 | ||
2287 | The @code{aio_fsync} and @code{aio_fsync64} functions are only available | |
19e4c7dd | 2288 | if the symbol @code{_POSIX_SYNCHRONIZED_IO} is defined in @file{unistd.h}. |
a3a4a74e UD |
2289 | |
2290 | @cindex synchronizing | |
2291 | @comment aio.h | |
2292 | @comment POSIX.1b | |
2293 | @deftypefun int aio_fsync (int @var{op}, struct aiocb *@var{aiocbp}) | |
2294 | Calling this function forces all I/O operations operating queued at the | |
fed8f7f7 | 2295 | time of the function call operating on the file descriptor |
a3a4a74e | 2296 | @code{aiocbp->aio_fildes} into the synchronized I/O completion state |
04b9968b | 2297 | (@pxref{Synchronizing I/O}). The @code{aio_fsync} function returns |
a3a4a74e UD |
2298 | immediately but the notification through the method described in |
2299 | @code{aiocbp->aio_sigevent} will happen only after all requests for this | |
04b9968b | 2300 | file descriptor have terminated and the file is synchronized. This also |
a3a4a74e | 2301 | means that requests for this very same file descriptor which are queued |
04b9968b | 2302 | after the synchronization request are not affected. |
a3a4a74e UD |
2303 | |
2304 | If @var{op} is @code{O_DSYNC} the synchronization happens as with a call | |
2305 | to @code{fdatasync}. Otherwise @var{op} should be @code{O_SYNC} and | |
fed8f7f7 | 2306 | the synchronization happens as with @code{fsync}. |
a3a4a74e | 2307 | |
19e4c7dd | 2308 | As long as the synchronization has not happened, a call to |
a3a4a74e | 2309 | @code{aio_error} with the reference to the object pointed to by |
fed8f7f7 UD |
2310 | @var{aiocbp} returns @code{EINPROGRESS}. Once the synchronization is |
2311 | done @code{aio_error} return @math{0} if the synchronization was not | |
a3a4a74e UD |
2312 | successful. Otherwise the value returned is the value to which the |
2313 | @code{fsync} or @code{fdatasync} function would have set the | |
2314 | @code{errno} variable. In this case nothing can be assumed about the | |
2315 | consistency for the data written to this file descriptor. | |
2316 | ||
2317 | The return value of this function is @math{0} if the request was | |
19e4c7dd | 2318 | successfully enqueued. Otherwise the return value is @math{-1} and |
a3a4a74e UD |
2319 | @code{errno} is set to one of the following values: |
2320 | ||
2321 | @table @code | |
2322 | @item EAGAIN | |
fed8f7f7 | 2323 | The request could not be enqueued due to temporary lack of resources. |
a3a4a74e UD |
2324 | @item EBADF |
2325 | The file descriptor @code{aiocbp->aio_fildes} is not valid or not open | |
2326 | for writing. | |
2327 | @item EINVAL | |
2328 | The implementation does not support I/O synchronization or the @var{op} | |
2329 | parameter is other than @code{O_DSYNC} and @code{O_SYNC}. | |
2330 | @item ENOSYS | |
2331 | This function is not implemented. | |
2332 | @end table | |
2333 | ||
2334 | When the sources are compiled with @code{_FILE_OFFSET_BITS == 64} this | |
37de3d55 | 2335 | function is in fact @code{aio_fsync64} since the LFS interface |
a3a4a74e UD |
2336 | transparently replaces the normal implementation. |
2337 | @end deftypefun | |
2338 | ||
2339 | @comment aio.h | |
2340 | @comment Unix98 | |
2341 | @deftypefun int aio_fsync64 (int @var{op}, struct aiocb64 *@var{aiocbp}) | |
2342 | This function is similar to @code{aio_fsync} with the only difference | |
2343 | that the argument is a reference to a variable of type @code{struct | |
2344 | aiocb64}. | |
2345 | ||
2346 | When the sources are compiled with @code{_FILE_OFFSET_BITS == 64} this | |
2347 | function is available under the name @code{aio_fsync} and so | |
04b9968b | 2348 | transparently replaces the interface for small files on 32 bit |
a3a4a74e UD |
2349 | machines. |
2350 | @end deftypefun | |
2351 | ||
fed8f7f7 | 2352 | Another method of synchronization is to wait until one or more requests of a |
a3a4a74e UD |
2353 | specific set terminated. This could be achieved by the @code{aio_*} |
2354 | functions to notify the initiating process about the termination but in | |
2355 | some situations this is not the ideal solution. In a program which | |
2356 | constantly updates clients somehow connected to the server it is not | |
2357 | always the best solution to go round robin since some connections might | |
2358 | be slow. On the other hand letting the @code{aio_*} function notify the | |
2359 | caller might also be not the best solution since whenever the process | |
2360 | works on preparing data for on client it makes no sense to be | |
2361 | interrupted by a notification since the new client will not be handled | |
2362 | before the current client is served. For situations like this | |
2363 | @code{aio_suspend} should be used. | |
2364 | ||
2365 | @comment aio.h | |
2366 | @comment POSIX.1b | |
2367 | @deftypefun int aio_suspend (const struct aiocb *const @var{list}[], int @var{nent}, const struct timespec *@var{timeout}) | |
19e4c7dd | 2368 | When calling this function, the calling thread is suspended until at |
a3a4a74e | 2369 | least one of the requests pointed to by the @var{nent} elements of the |
19e4c7dd AJ |
2370 | array @var{list} has completed. If any of the requests has already |
2371 | completed at the time @code{aio_suspend} is called, the function returns | |
2372 | immediately. Whether a request has terminated or not is determined by | |
a3a4a74e | 2373 | comparing the error status of the request with @code{EINPROGRESS}. If |
19e4c7dd | 2374 | an element of @var{list} is @code{NULL}, the entry is simply ignored. |
a3a4a74e | 2375 | |
19e4c7dd AJ |
2376 | If no request has finished, the calling process is suspended. If |
2377 | @var{timeout} is @code{NULL}, the process is not woken until a request | |
2378 | has finished. If @var{timeout} is not @code{NULL}, the process remains | |
2379 | suspended at least as long as specified in @var{timeout}. In this case, | |
a3a4a74e UD |
2380 | @code{aio_suspend} returns with an error. |
2381 | ||
fed8f7f7 | 2382 | The return value of the function is @math{0} if one or more requests |
a3a4a74e UD |
2383 | from the @var{list} have terminated. Otherwise the function returns |
2384 | @math{-1} and @code{errno} is set to one of the following values: | |
2385 | ||
2386 | @table @code | |
2387 | @item EAGAIN | |
2388 | None of the requests from the @var{list} completed in the time specified | |
2389 | by @var{timeout}. | |
2390 | @item EINTR | |
2391 | A signal interrupted the @code{aio_suspend} function. This signal might | |
2392 | also be sent by the AIO implementation while signalling the termination | |
2393 | of one of the requests. | |
2394 | @item ENOSYS | |
2395 | The @code{aio_suspend} function is not implemented. | |
2396 | @end table | |
2397 | ||
2398 | When the sources are compiled with @code{_FILE_OFFSET_BITS == 64} this | |
2399 | function is in fact @code{aio_suspend64} since the LFS interface | |
2400 | transparently replaces the normal implementation. | |
2401 | @end deftypefun | |
2402 | ||
2403 | @comment aio.h | |
2404 | @comment Unix98 | |
2405 | @deftypefun int aio_suspend64 (const struct aiocb64 *const @var{list}[], int @var{nent}, const struct timespec *@var{timeout}) | |
2406 | This function is similar to @code{aio_suspend} with the only difference | |
2407 | that the argument is a reference to a variable of type @code{struct | |
2408 | aiocb64}. | |
2409 | ||
2410 | When the sources are compiled with @code{_FILE_OFFSET_BITS == 64} this | |
2411 | function is available under the name @code{aio_suspend} and so | |
04b9968b | 2412 | transparently replaces the interface for small files on 32 bit |
a3a4a74e UD |
2413 | machines. |
2414 | @end deftypefun | |
b07d03e0 UD |
2415 | |
2416 | @node Cancel AIO Operations | |
04b9968b | 2417 | @subsection Cancellation of AIO Operations |
b07d03e0 | 2418 | |
19e4c7dd | 2419 | When one or more requests are asynchronously processed, it might be |
a3a4a74e | 2420 | useful in some situations to cancel a selected operation, e.g., if it |
19e4c7dd AJ |
2421 | becomes obvious that the written data is no longer accurate and would |
2422 | have to be overwritten soon. As an example, assume an application, which | |
a3a4a74e UD |
2423 | writes data in files in a situation where new incoming data would have |
2424 | to be written in a file which will be updated by an enqueued request. | |
19e4c7dd AJ |
2425 | The POSIX AIO implementation provides such a function, but this function |
2426 | is not capable of forcing the cancellation of the request. It is up to the | |
a3a4a74e UD |
2427 | implementation to decide whether it is possible to cancel the operation |
2428 | or not. Therefore using this function is merely a hint. | |
2429 | ||
2430 | @comment aio.h | |
2431 | @comment POSIX.1b | |
2432 | @deftypefun int aio_cancel (int @var{fildes}, struct aiocb *@var{aiocbp}) | |
2433 | The @code{aio_cancel} function can be used to cancel one or more | |
19e4c7dd AJ |
2434 | outstanding requests. If the @var{aiocbp} parameter is @code{NULL}, the |
2435 | function tries to cancel all of the outstanding requests which would process | |
2436 | the file descriptor @var{fildes} (i.e., whose @code{aio_fildes} member | |
2437 | is @var{fildes}). If @var{aiocbp} is not @code{NULL}, @code{aio_cancel} | |
2438 | attempts to cancel the specific request pointed to by @var{aiocbp}. | |
a3a4a74e | 2439 | |
19e4c7dd | 2440 | For requests which were successfully canceled, the normal notification |
a3a4a74e UD |
2441 | about the termination of the request should take place. I.e., depending |
2442 | on the @code{struct sigevent} object which controls this, nothing | |
2443 | happens, a signal is sent or a thread is started. If the request cannot | |
19e4c7dd | 2444 | be canceled, it terminates the usual way after performing the operation. |
a3a4a74e | 2445 | |
19e4c7dd | 2446 | After a request is successfully canceled, a call to @code{aio_error} with |
a3a4a74e UD |
2447 | a reference to this request as the parameter will return |
2448 | @code{ECANCELED} and a call to @code{aio_return} will return @math{-1}. | |
19e4c7dd | 2449 | If the request wasn't canceled and is still running the error status is |
a3a4a74e UD |
2450 | still @code{EINPROGRESS}. |
2451 | ||
2452 | The return value of the function is @code{AIO_CANCELED} if there were | |
19e4c7dd AJ |
2453 | requests which haven't terminated and which were successfully canceled. |
2454 | If there is one or more requests left which couldn't be canceled, the | |
a3a4a74e | 2455 | return value is @code{AIO_NOTCANCELED}. In this case @code{aio_error} |
19e4c7dd AJ |
2456 | must be used to find out which of the, perhaps multiple, requests (in |
2457 | @var{aiocbp} is @code{NULL}) weren't successfully canceled. If all | |
a3a4a74e UD |
2458 | requests already terminated at the time @code{aio_cancel} is called the |
2459 | return value is @code{AIO_ALLDONE}. | |
2460 | ||
2461 | If an error occurred during the execution of @code{aio_cancel} the | |
2462 | function returns @math{-1} and sets @code{errno} to one of the following | |
2463 | values. | |
2464 | ||
2465 | @table @code | |
2466 | @item EBADF | |
2467 | The file descriptor @var{fildes} is not valid. | |
2468 | @item ENOSYS | |
2469 | @code{aio_cancel} is not implemented. | |
2470 | @end table | |
2471 | ||
19e4c7dd | 2472 | When the sources are compiled with @code{_FILE_OFFSET_BITS == 64}, this |
a3a4a74e UD |
2473 | function is in fact @code{aio_cancel64} since the LFS interface |
2474 | transparently replaces the normal implementation. | |
2475 | @end deftypefun | |
2476 | ||
2477 | @comment aio.h | |
2478 | @comment Unix98 | |
19e4c7dd | 2479 | @deftypefun int aio_cancel64 (int @var{fildes}, struct aiocb64 *@var{aiocbp}) |
a3a4a74e UD |
2480 | This function is similar to @code{aio_cancel} with the only difference |
2481 | that the argument is a reference to a variable of type @code{struct | |
2482 | aiocb64}. | |
2483 | ||
19e4c7dd | 2484 | When the sources are compiled with @code{_FILE_OFFSET_BITS == 64}, this |
a3a4a74e | 2485 | function is available under the name @code{aio_cancel} and so |
04b9968b | 2486 | transparently replaces the interface for small files on 32 bit |
a3a4a74e UD |
2487 | machines. |
2488 | @end deftypefun | |
2489 | ||
2490 | @node Configuration of AIO | |
2491 | @subsection How to optimize the AIO implementation | |
2492 | ||
2493 | The POSIX standard does not specify how the AIO functions are | |
19e4c7dd | 2494 | implemented. They could be system calls, but it is also possible to |
a3a4a74e UD |
2495 | emulate them at userlevel. |
2496 | ||
19e4c7dd AJ |
2497 | At the point of this writing, the available implementation is a userlevel |
2498 | implementation which uses threads for handling the enqueued requests. | |
2499 | While this implementation requires making some decisions about | |
2500 | limitations, hard limitations are something which is best avoided | |
1f77f049 | 2501 | in @theglibc{}. Therefore, @theglibc{} provides a means |
19e4c7dd | 2502 | for tuning the AIO implementation according to the individual use. |
a3a4a74e UD |
2503 | |
2504 | @comment aio.h | |
2505 | @comment GNU | |
2506 | @deftp {Data Type} {struct aioinit} | |
2507 | This data type is used to pass the configuration or tunable parameters | |
2508 | to the implementation. The program has to initialize the members of | |
2509 | this struct and pass it to the implementation using the @code{aio_init} | |
2510 | function. | |
2511 | ||
2512 | @table @code | |
2513 | @item int aio_threads | |
19e4c7dd | 2514 | This member specifies the maximal number of threads which may be used |
a3a4a74e UD |
2515 | at any one time. |
2516 | @item int aio_num | |
c756c71c | 2517 | This number provides an estimate on the maximal number of simultaneously |
a3a4a74e UD |
2518 | enqueued requests. |
2519 | @item int aio_locks | |
19e4c7dd | 2520 | Unused. |
a3a4a74e | 2521 | @item int aio_usedba |
19e4c7dd | 2522 | Unused. |
a3a4a74e | 2523 | @item int aio_debug |
19e4c7dd | 2524 | Unused. |
a3a4a74e | 2525 | @item int aio_numusers |
19e4c7dd | 2526 | Unused. |
a3a4a74e | 2527 | @item int aio_reserved[2] |
19e4c7dd | 2528 | Unused. |
a3a4a74e UD |
2529 | @end table |
2530 | @end deftp | |
2531 | ||
2532 | @comment aio.h | |
2533 | @comment GNU | |
2534 | @deftypefun void aio_init (const struct aioinit *@var{init}) | |
2535 | This function must be called before any other AIO function. Calling it | |
19e4c7dd AJ |
2536 | is completely voluntary, as it is only meant to help the AIO |
2537 | implementation perform better. | |
a3a4a74e | 2538 | |
19e4c7dd | 2539 | Before calling the @code{aio_init}, function the members of a variable of |
a3a4a74e UD |
2540 | type @code{struct aioinit} must be initialized. Then a reference to |
2541 | this variable is passed as the parameter to @code{aio_init} which itself | |
2542 | may or may not pay attention to the hints. | |
2543 | ||
c756c71c UD |
2544 | The function has no return value and no error cases are defined. It is |
2545 | a extension which follows a proposal from the SGI implementation in | |
2546 | @w{Irix 6}. It is not covered by POSIX.1b or Unix98. | |
a3a4a74e | 2547 | @end deftypefun |
b07d03e0 | 2548 | |
28f540f4 RM |
2549 | @node Control Operations |
2550 | @section Control Operations on Files | |
2551 | ||
2552 | @cindex control operations on files | |
2553 | @cindex @code{fcntl} function | |
2554 | This section describes how you can perform various other operations on | |
2555 | file descriptors, such as inquiring about or setting flags describing | |
2556 | the status of the file descriptor, manipulating record locks, and the | |
2557 | like. All of these operations are performed by the function @code{fcntl}. | |
2558 | ||
2559 | The second argument to the @code{fcntl} function is a command that | |
2560 | specifies which operation to perform. The function and macros that name | |
2561 | various flags that are used with it are declared in the header file | |
2562 | @file{fcntl.h}. Many of these flags are also used by the @code{open} | |
2563 | function; see @ref{Opening and Closing Files}. | |
2564 | @pindex fcntl.h | |
2565 | ||
2566 | @comment fcntl.h | |
2567 | @comment POSIX.1 | |
2568 | @deftypefun int fcntl (int @var{filedes}, int @var{command}, @dots{}) | |
2569 | The @code{fcntl} function performs the operation specified by | |
2570 | @var{command} on the file descriptor @var{filedes}. Some commands | |
2571 | require additional arguments to be supplied. These additional arguments | |
2572 | and the return value and error conditions are given in the detailed | |
2573 | descriptions of the individual commands. | |
2574 | ||
2575 | Briefly, here is a list of what the various commands are. | |
2576 | ||
2577 | @table @code | |
2578 | @item F_DUPFD | |
2579 | Duplicate the file descriptor (return another file descriptor pointing | |
2580 | to the same open file). @xref{Duplicating Descriptors}. | |
2581 | ||
2582 | @item F_GETFD | |
2583 | Get flags associated with the file descriptor. @xref{Descriptor Flags}. | |
2584 | ||
2585 | @item F_SETFD | |
2586 | Set flags associated with the file descriptor. @xref{Descriptor Flags}. | |
2587 | ||
2588 | @item F_GETFL | |
2589 | Get flags associated with the open file. @xref{File Status Flags}. | |
2590 | ||
2591 | @item F_SETFL | |
2592 | Set flags associated with the open file. @xref{File Status Flags}. | |
2593 | ||
2594 | @item F_GETLK | |
2595 | Get a file lock. @xref{File Locks}. | |
2596 | ||
2597 | @item F_SETLK | |
2598 | Set or clear a file lock. @xref{File Locks}. | |
2599 | ||
2600 | @item F_SETLKW | |
2601 | Like @code{F_SETLK}, but wait for completion. @xref{File Locks}. | |
2602 | ||
2603 | @item F_GETOWN | |
2604 | Get process or process group ID to receive @code{SIGIO} signals. | |
2605 | @xref{Interrupt Input}. | |
2606 | ||
2607 | @item F_SETOWN | |
2608 | Set process or process group ID to receive @code{SIGIO} signals. | |
2609 | @xref{Interrupt Input}. | |
2610 | @end table | |
dfd2257a | 2611 | |
04b9968b | 2612 | This function is a cancellation point in multi-threaded programs. This |
dfd2257a UD |
2613 | is a problem if the thread allocates some resources (like memory, file |
2614 | descriptors, semaphores or whatever) at the time @code{fcntl} is | |
19e4c7dd | 2615 | called. If the thread gets canceled these resources stay allocated |
dfd2257a | 2616 | until the program ends. To avoid this calls to @code{fcntl} should be |
04b9968b | 2617 | protected using cancellation handlers. |
dfd2257a | 2618 | @c ref pthread_cleanup_push / pthread_cleanup_pop |
28f540f4 RM |
2619 | @end deftypefun |
2620 | ||
2621 | ||
2622 | @node Duplicating Descriptors | |
2623 | @section Duplicating Descriptors | |
2624 | ||
2625 | @cindex duplicating file descriptors | |
2626 | @cindex redirecting input and output | |
2627 | ||
2628 | You can @dfn{duplicate} a file descriptor, or allocate another file | |
2629 | descriptor that refers to the same open file as the original. Duplicate | |
2630 | descriptors share one file position and one set of file status flags | |
2631 | (@pxref{File Status Flags}), but each has its own set of file descriptor | |
2632 | flags (@pxref{Descriptor Flags}). | |
2633 | ||
2634 | The major use of duplicating a file descriptor is to implement | |
2635 | @dfn{redirection} of input or output: that is, to change the | |
2636 | file or pipe that a particular file descriptor corresponds to. | |
2637 | ||
2638 | You can perform this operation using the @code{fcntl} function with the | |
2639 | @code{F_DUPFD} command, but there are also convenient functions | |
2640 | @code{dup} and @code{dup2} for duplicating descriptors. | |
2641 | ||
2642 | @pindex unistd.h | |
2643 | @pindex fcntl.h | |
2644 | The @code{fcntl} function and flags are declared in @file{fcntl.h}, | |
2645 | while prototypes for @code{dup} and @code{dup2} are in the header file | |
2646 | @file{unistd.h}. | |
2647 | ||
2648 | @comment unistd.h | |
2649 | @comment POSIX.1 | |
2650 | @deftypefun int dup (int @var{old}) | |
2651 | This function copies descriptor @var{old} to the first available | |
2652 | descriptor number (the first number not currently open). It is | |
2653 | equivalent to @code{fcntl (@var{old}, F_DUPFD, 0)}. | |
2654 | @end deftypefun | |
2655 | ||
2656 | @comment unistd.h | |
2657 | @comment POSIX.1 | |
2658 | @deftypefun int dup2 (int @var{old}, int @var{new}) | |
2659 | This function copies the descriptor @var{old} to descriptor number | |
2660 | @var{new}. | |
2661 | ||
2662 | If @var{old} is an invalid descriptor, then @code{dup2} does nothing; it | |
2663 | does not close @var{new}. Otherwise, the new duplicate of @var{old} | |
2664 | replaces any previous meaning of descriptor @var{new}, as if @var{new} | |
2665 | were closed first. | |
2666 | ||
2667 | If @var{old} and @var{new} are different numbers, and @var{old} is a | |
2668 | valid descriptor number, then @code{dup2} is equivalent to: | |
2669 | ||
2670 | @smallexample | |
2671 | close (@var{new}); | |
2672 | fcntl (@var{old}, F_DUPFD, @var{new}) | |
2673 | @end smallexample | |
2674 | ||
2675 | However, @code{dup2} does this atomically; there is no instant in the | |
2676 | middle of calling @code{dup2} at which @var{new} is closed and not yet a | |
2677 | duplicate of @var{old}. | |
2678 | @end deftypefun | |
2679 | ||
2680 | @comment fcntl.h | |
2681 | @comment POSIX.1 | |
2682 | @deftypevr Macro int F_DUPFD | |
2683 | This macro is used as the @var{command} argument to @code{fcntl}, to | |
2684 | copy the file descriptor given as the first argument. | |
2685 | ||
2686 | The form of the call in this case is: | |
2687 | ||
2688 | @smallexample | |
2689 | fcntl (@var{old}, F_DUPFD, @var{next-filedes}) | |
2690 | @end smallexample | |
2691 | ||
2692 | The @var{next-filedes} argument is of type @code{int} and specifies that | |
2693 | the file descriptor returned should be the next available one greater | |
2694 | than or equal to this value. | |
2695 | ||
2696 | The return value from @code{fcntl} with this command is normally the value | |
07435eb4 | 2697 | of the new file descriptor. A return value of @math{-1} indicates an |
28f540f4 RM |
2698 | error. The following @code{errno} error conditions are defined for |
2699 | this command: | |
2700 | ||
2701 | @table @code | |
2702 | @item EBADF | |
2703 | The @var{old} argument is invalid. | |
2704 | ||
2705 | @item EINVAL | |
2706 | The @var{next-filedes} argument is invalid. | |
2707 | ||
2708 | @item EMFILE | |
2709 | There are no more file descriptors available---your program is already | |
2710 | using the maximum. In BSD and GNU, the maximum is controlled by a | |
2711 | resource limit that can be changed; @pxref{Limits on Resources}, for | |
2712 | more information about the @code{RLIMIT_NOFILE} limit. | |
2713 | @end table | |
2714 | ||
2715 | @code{ENFILE} is not a possible error code for @code{dup2} because | |
2716 | @code{dup2} does not create a new opening of a file; duplicate | |
2717 | descriptors do not count toward the limit which @code{ENFILE} | |
2718 | indicates. @code{EMFILE} is possible because it refers to the limit on | |
2719 | distinct descriptor numbers in use in one process. | |
2720 | @end deftypevr | |
2721 | ||
2722 | Here is an example showing how to use @code{dup2} to do redirection. | |
2723 | Typically, redirection of the standard streams (like @code{stdin}) is | |
2724 | done by a shell or shell-like program before calling one of the | |
2725 | @code{exec} functions (@pxref{Executing a File}) to execute a new | |
2726 | program in a child process. When the new program is executed, it | |
2727 | creates and initializes the standard streams to point to the | |
2728 | corresponding file descriptors, before its @code{main} function is | |
2729 | invoked. | |
2730 | ||
2731 | So, to redirect standard input to a file, the shell could do something | |
2732 | like: | |
2733 | ||
2734 | @smallexample | |
2735 | pid = fork (); | |
2736 | if (pid == 0) | |
2737 | @{ | |
2738 | char *filename; | |
2739 | char *program; | |
2740 | int file; | |
2741 | @dots{} | |
2742 | file = TEMP_FAILURE_RETRY (open (filename, O_RDONLY)); | |
2743 | dup2 (file, STDIN_FILENO); | |
2744 | TEMP_FAILURE_RETRY (close (file)); | |
2745 | execv (program, NULL); | |
2746 | @} | |
2747 | @end smallexample | |
2748 | ||
2749 | There is also a more detailed example showing how to implement redirection | |
2750 | in the context of a pipeline of processes in @ref{Launching Jobs}. | |
2751 | ||
2752 | ||
2753 | @node Descriptor Flags | |
2754 | @section File Descriptor Flags | |
2755 | @cindex file descriptor flags | |
2756 | ||
2757 | @dfn{File descriptor flags} are miscellaneous attributes of a file | |
2758 | descriptor. These flags are associated with particular file | |
2759 | descriptors, so that if you have created duplicate file descriptors | |
2760 | from a single opening of a file, each descriptor has its own set of flags. | |
2761 | ||
2762 | Currently there is just one file descriptor flag: @code{FD_CLOEXEC}, | |
2763 | which causes the descriptor to be closed if you use any of the | |
2764 | @code{exec@dots{}} functions (@pxref{Executing a File}). | |
2765 | ||
2766 | The symbols in this section are defined in the header file | |
2767 | @file{fcntl.h}. | |
2768 | @pindex fcntl.h | |
2769 | ||
2770 | @comment fcntl.h | |
2771 | @comment POSIX.1 | |
2772 | @deftypevr Macro int F_GETFD | |
2773 | This macro is used as the @var{command} argument to @code{fcntl}, to | |
2774 | specify that it should return the file descriptor flags associated | |
2c6fe0bd | 2775 | with the @var{filedes} argument. |
28f540f4 RM |
2776 | |
2777 | The normal return value from @code{fcntl} with this command is a | |
2778 | nonnegative number which can be interpreted as the bitwise OR of the | |
2779 | individual flags (except that currently there is only one flag to use). | |
2780 | ||
07435eb4 | 2781 | In case of an error, @code{fcntl} returns @math{-1}. The following |
28f540f4 RM |
2782 | @code{errno} error conditions are defined for this command: |
2783 | ||
2784 | @table @code | |
2785 | @item EBADF | |
2786 | The @var{filedes} argument is invalid. | |
2787 | @end table | |
2788 | @end deftypevr | |
2789 | ||
2790 | ||
2791 | @comment fcntl.h | |
2792 | @comment POSIX.1 | |
2793 | @deftypevr Macro int F_SETFD | |
2794 | This macro is used as the @var{command} argument to @code{fcntl}, to | |
2795 | specify that it should set the file descriptor flags associated with the | |
2796 | @var{filedes} argument. This requires a third @code{int} argument to | |
2797 | specify the new flags, so the form of the call is: | |
2798 | ||
2799 | @smallexample | |
2800 | fcntl (@var{filedes}, F_SETFD, @var{new-flags}) | |
2801 | @end smallexample | |
2802 | ||
2803 | The normal return value from @code{fcntl} with this command is an | |
07435eb4 | 2804 | unspecified value other than @math{-1}, which indicates an error. |
28f540f4 RM |
2805 | The flags and error conditions are the same as for the @code{F_GETFD} |
2806 | command. | |
2807 | @end deftypevr | |
2808 | ||
2809 | The following macro is defined for use as a file descriptor flag with | |
2810 | the @code{fcntl} function. The value is an integer constant usable | |
2811 | as a bit mask value. | |
2812 | ||
2813 | @comment fcntl.h | |
2814 | @comment POSIX.1 | |
2815 | @deftypevr Macro int FD_CLOEXEC | |
2816 | @cindex close-on-exec (file descriptor flag) | |
2817 | This flag specifies that the file descriptor should be closed when | |
2818 | an @code{exec} function is invoked; see @ref{Executing a File}. When | |
2819 | a file descriptor is allocated (as with @code{open} or @code{dup}), | |
2820 | this bit is initially cleared on the new file descriptor, meaning that | |
2821 | descriptor will survive into the new program after @code{exec}. | |
2822 | @end deftypevr | |
2823 | ||
2824 | If you want to modify the file descriptor flags, you should get the | |
2825 | current flags with @code{F_GETFD} and modify the value. Don't assume | |
2826 | that the flags listed here are the only ones that are implemented; your | |
2827 | program may be run years from now and more flags may exist then. For | |
2828 | example, here is a function to set or clear the flag @code{FD_CLOEXEC} | |
2829 | without altering any other flags: | |
2830 | ||
2831 | @smallexample | |
2832 | /* @r{Set the @code{FD_CLOEXEC} flag of @var{desc} if @var{value} is nonzero,} | |
2833 | @r{or clear the flag if @var{value} is 0.} | |
2c6fe0bd | 2834 | @r{Return 0 on success, or -1 on error with @code{errno} set.} */ |
28f540f4 RM |
2835 | |
2836 | int | |
2837 | set_cloexec_flag (int desc, int value) | |
2838 | @{ | |
2839 | int oldflags = fcntl (desc, F_GETFD, 0); | |
8e96ae1a | 2840 | /* @r{If reading the flags failed, return error indication now.} */ |
28f540f4 RM |
2841 | if (oldflags < 0) |
2842 | return oldflags; | |
2843 | /* @r{Set just the flag we want to set.} */ | |
2844 | if (value != 0) | |
2845 | oldflags |= FD_CLOEXEC; | |
2846 | else | |
2847 | oldflags &= ~FD_CLOEXEC; | |
2848 | /* @r{Store modified flag word in the descriptor.} */ | |
2849 | return fcntl (desc, F_SETFD, oldflags); | |
2850 | @} | |
2851 | @end smallexample | |
2852 | ||
2853 | @node File Status Flags | |
2854 | @section File Status Flags | |
2855 | @cindex file status flags | |
2856 | ||
2857 | @dfn{File status flags} are used to specify attributes of the opening of a | |
2858 | file. Unlike the file descriptor flags discussed in @ref{Descriptor | |
2859 | Flags}, the file status flags are shared by duplicated file descriptors | |
2860 | resulting from a single opening of the file. The file status flags are | |
2861 | specified with the @var{flags} argument to @code{open}; | |
2862 | @pxref{Opening and Closing Files}. | |
2863 | ||
2864 | File status flags fall into three categories, which are described in the | |
2865 | following sections. | |
2866 | ||
2867 | @itemize @bullet | |
2868 | @item | |
2869 | @ref{Access Modes}, specify what type of access is allowed to the | |
2870 | file: reading, writing, or both. They are set by @code{open} and are | |
2871 | returned by @code{fcntl}, but cannot be changed. | |
2872 | ||
2873 | @item | |
2874 | @ref{Open-time Flags}, control details of what @code{open} will do. | |
2875 | These flags are not preserved after the @code{open} call. | |
2876 | ||
2877 | @item | |
2878 | @ref{Operating Modes}, affect how operations such as @code{read} and | |
2879 | @code{write} are done. They are set by @code{open}, and can be fetched or | |
2880 | changed with @code{fcntl}. | |
2881 | @end itemize | |
2882 | ||
2883 | The symbols in this section are defined in the header file | |
2884 | @file{fcntl.h}. | |
2885 | @pindex fcntl.h | |
2886 | ||
2887 | @menu | |
2888 | * Access Modes:: Whether the descriptor can read or write. | |
2889 | * Open-time Flags:: Details of @code{open}. | |
2890 | * Operating Modes:: Special modes to control I/O operations. | |
2891 | * Getting File Status Flags:: Fetching and changing these flags. | |
2892 | @end menu | |
2893 | ||
2894 | @node Access Modes | |
2895 | @subsection File Access Modes | |
2896 | ||
2897 | The file access modes allow a file descriptor to be used for reading, | |
a7a93d50 | 2898 | writing, or both. (On @gnuhurdsystems{}, they can also allow none of these, |
28f540f4 RM |
2899 | and allow execution of the file as a program.) The access modes are chosen |
2900 | when the file is opened, and never change. | |
2901 | ||
2902 | @comment fcntl.h | |
2903 | @comment POSIX.1 | |
2904 | @deftypevr Macro int O_RDONLY | |
2905 | Open the file for read access. | |
2906 | @end deftypevr | |
2907 | ||
2908 | @comment fcntl.h | |
2909 | @comment POSIX.1 | |
2910 | @deftypevr Macro int O_WRONLY | |
2911 | Open the file for write access. | |
2912 | @end deftypevr | |
2913 | ||
2914 | @comment fcntl.h | |
2915 | @comment POSIX.1 | |
2916 | @deftypevr Macro int O_RDWR | |
2917 | Open the file for both reading and writing. | |
2918 | @end deftypevr | |
2919 | ||
a7a93d50 | 2920 | On @gnuhurdsystems{} (and not on other systems), @code{O_RDONLY} and |
28f540f4 RM |
2921 | @code{O_WRONLY} are independent bits that can be bitwise-ORed together, |
2922 | and it is valid for either bit to be set or clear. This means that | |
2923 | @code{O_RDWR} is the same as @code{O_RDONLY|O_WRONLY}. A file access | |
2924 | mode of zero is permissible; it allows no operations that do input or | |
2925 | output to the file, but does allow other operations such as | |
a7a93d50 | 2926 | @code{fchmod}. On @gnuhurdsystems{}, since ``read-only'' or ``write-only'' |
28f540f4 RM |
2927 | is a misnomer, @file{fcntl.h} defines additional names for the file |
2928 | access modes. These names are preferred when writing GNU-specific code. | |
2929 | But most programs will want to be portable to other POSIX.1 systems and | |
2930 | should use the POSIX.1 names above instead. | |
2931 | ||
2932 | @comment fcntl.h | |
2933 | @comment GNU | |
2934 | @deftypevr Macro int O_READ | |
c2835376 | 2935 | Open the file for reading. Same as @code{O_RDONLY}; only defined on GNU. |
28f540f4 RM |
2936 | @end deftypevr |
2937 | ||
2938 | @comment fcntl.h | |
2939 | @comment GNU | |
2940 | @deftypevr Macro int O_WRITE | |
c2835376 | 2941 | Open the file for writing. Same as @code{O_WRONLY}; only defined on GNU. |
28f540f4 RM |
2942 | @end deftypevr |
2943 | ||
2944 | @comment fcntl.h | |
2945 | @comment GNU | |
2946 | @deftypevr Macro int O_EXEC | |
2947 | Open the file for executing. Only defined on GNU. | |
2948 | @end deftypevr | |
2949 | ||
2950 | To determine the file access mode with @code{fcntl}, you must extract | |
a7a93d50 JM |
2951 | the access mode bits from the retrieved file status flags. On |
2952 | @gnuhurdsystems{}, | |
2953 | you can just test the @code{O_READ} and @code{O_WRITE} bits in | |
28f540f4 RM |
2954 | the flags word. But in other POSIX.1 systems, reading and writing |
2955 | access modes are not stored as distinct bit flags. The portable way to | |
2956 | extract the file access mode bits is with @code{O_ACCMODE}. | |
2957 | ||
2958 | @comment fcntl.h | |
2959 | @comment POSIX.1 | |
2960 | @deftypevr Macro int O_ACCMODE | |
2961 | This macro stands for a mask that can be bitwise-ANDed with the file | |
2962 | status flag value to produce a value representing the file access mode. | |
2963 | The mode will be @code{O_RDONLY}, @code{O_WRONLY}, or @code{O_RDWR}. | |
a7a93d50 | 2964 | (On @gnuhurdsystems{} it could also be zero, and it never includes the |
28f540f4 RM |
2965 | @code{O_EXEC} bit.) |
2966 | @end deftypevr | |
2967 | ||
2968 | @node Open-time Flags | |
2969 | @subsection Open-time Flags | |
2970 | ||
2971 | The open-time flags specify options affecting how @code{open} will behave. | |
2972 | These options are not preserved once the file is open. The exception to | |
2973 | this is @code{O_NONBLOCK}, which is also an I/O operating mode and so it | |
2974 | @emph{is} saved. @xref{Opening and Closing Files}, for how to call | |
2975 | @code{open}. | |
2976 | ||
2977 | There are two sorts of options specified by open-time flags. | |
2978 | ||
2979 | @itemize @bullet | |
2980 | @item | |
2981 | @dfn{File name translation flags} affect how @code{open} looks up the | |
2982 | file name to locate the file, and whether the file can be created. | |
2983 | @cindex file name translation flags | |
2984 | @cindex flags, file name translation | |
2985 | ||
2986 | @item | |
2987 | @dfn{Open-time action flags} specify extra operations that @code{open} will | |
2988 | perform on the file once it is open. | |
2989 | @cindex open-time action flags | |
2990 | @cindex flags, open-time action | |
2991 | @end itemize | |
2992 | ||
2993 | Here are the file name translation flags. | |
2994 | ||
2995 | @comment fcntl.h | |
2996 | @comment POSIX.1 | |
2997 | @deftypevr Macro int O_CREAT | |
2998 | If set, the file will be created if it doesn't already exist. | |
2999 | @c !!! mode arg, umask | |
3000 | @cindex create on open (file status flag) | |
3001 | @end deftypevr | |
3002 | ||
3003 | @comment fcntl.h | |
3004 | @comment POSIX.1 | |
3005 | @deftypevr Macro int O_EXCL | |
3006 | If both @code{O_CREAT} and @code{O_EXCL} are set, then @code{open} fails | |
3007 | if the specified file already exists. This is guaranteed to never | |
3008 | clobber an existing file. | |
3009 | @end deftypevr | |
3010 | ||
3011 | @comment fcntl.h | |
3012 | @comment POSIX.1 | |
3013 | @deftypevr Macro int O_NONBLOCK | |
3014 | @cindex non-blocking open | |
3015 | This prevents @code{open} from blocking for a ``long time'' to open the | |
3016 | file. This is only meaningful for some kinds of files, usually devices | |
3017 | such as serial ports; when it is not meaningful, it is harmless and | |
3018 | ignored. Often opening a port to a modem blocks until the modem reports | |
3019 | carrier detection; if @code{O_NONBLOCK} is specified, @code{open} will | |
3020 | return immediately without a carrier. | |
3021 | ||
3022 | Note that the @code{O_NONBLOCK} flag is overloaded as both an I/O operating | |
3023 | mode and a file name translation flag. This means that specifying | |
3024 | @code{O_NONBLOCK} in @code{open} also sets nonblocking I/O mode; | |
3025 | @pxref{Operating Modes}. To open the file without blocking but do normal | |
3026 | I/O that blocks, you must call @code{open} with @code{O_NONBLOCK} set and | |
3027 | then call @code{fcntl} to turn the bit off. | |
3028 | @end deftypevr | |
3029 | ||
3030 | @comment fcntl.h | |
3031 | @comment POSIX.1 | |
3032 | @deftypevr Macro int O_NOCTTY | |
3033 | If the named file is a terminal device, don't make it the controlling | |
3034 | terminal for the process. @xref{Job Control}, for information about | |
3035 | what it means to be the controlling terminal. | |
3036 | ||
a7a93d50 JM |
3037 | On @gnuhurdsystems{} and 4.4 BSD, opening a file never makes it the |
3038 | controlling terminal and @code{O_NOCTTY} is zero. However, @gnulinuxsystems{} | |
3039 | and some other systems use a nonzero value for @code{O_NOCTTY} and set the | |
28f540f4 RM |
3040 | controlling terminal when you open a file that is a terminal device; so |
3041 | to be portable, use @code{O_NOCTTY} when it is important to avoid this. | |
3042 | @cindex controlling terminal, setting | |
3043 | @end deftypevr | |
3044 | ||
a7a93d50 JM |
3045 | The following three file name translation flags exist only on |
3046 | @gnuhurdsystems{}. | |
28f540f4 RM |
3047 | |
3048 | @comment fcntl.h | |
3049 | @comment GNU | |
3050 | @deftypevr Macro int O_IGNORE_CTTY | |
3051 | Do not recognize the named file as the controlling terminal, even if it | |
3052 | refers to the process's existing controlling terminal device. Operations | |
3053 | on the new file descriptor will never induce job control signals. | |
3054 | @xref{Job Control}. | |
3055 | @end deftypevr | |
3056 | ||
3057 | @comment fcntl.h | |
3058 | @comment GNU | |
3059 | @deftypevr Macro int O_NOLINK | |
3060 | If the named file is a symbolic link, open the link itself instead of | |
3061 | the file it refers to. (@code{fstat} on the new file descriptor will | |
3062 | return the information returned by @code{lstat} on the link's name.) | |
3063 | @cindex symbolic link, opening | |
3064 | @end deftypevr | |
3065 | ||
3066 | @comment fcntl.h | |
3067 | @comment GNU | |
3068 | @deftypevr Macro int O_NOTRANS | |
3069 | If the named file is specially translated, do not invoke the translator. | |
3070 | Open the bare file the translator itself sees. | |
3071 | @end deftypevr | |
3072 | ||
3073 | ||
3074 | The open-time action flags tell @code{open} to do additional operations | |
3075 | which are not really related to opening the file. The reason to do them | |
3076 | as part of @code{open} instead of in separate calls is that @code{open} | |
3077 | can do them @i{atomically}. | |
3078 | ||
3079 | @comment fcntl.h | |
3080 | @comment POSIX.1 | |
3081 | @deftypevr Macro int O_TRUNC | |
3082 | Truncate the file to zero length. This option is only useful for | |
3083 | regular files, not special files such as directories or FIFOs. POSIX.1 | |
3084 | requires that you open the file for writing to use @code{O_TRUNC}. In | |
3085 | BSD and GNU you must have permission to write the file to truncate it, | |
3086 | but you need not open for write access. | |
3087 | ||
3088 | This is the only open-time action flag specified by POSIX.1. There is | |
3089 | no good reason for truncation to be done by @code{open}, instead of by | |
3090 | calling @code{ftruncate} afterwards. The @code{O_TRUNC} flag existed in | |
3091 | Unix before @code{ftruncate} was invented, and is retained for backward | |
3092 | compatibility. | |
3093 | @end deftypevr | |
3094 | ||
27e309c1 UD |
3095 | The remaining operating modes are BSD extensions. They exist only |
3096 | on some systems. On other systems, these macros are not defined. | |
3097 | ||
28f540f4 RM |
3098 | @comment fcntl.h |
3099 | @comment BSD | |
3100 | @deftypevr Macro int O_SHLOCK | |
3101 | Acquire a shared lock on the file, as with @code{flock}. | |
3102 | @xref{File Locks}. | |
3103 | ||
3104 | If @code{O_CREAT} is specified, the locking is done atomically when | |
3105 | creating the file. You are guaranteed that no other process will get | |
3106 | the lock on the new file first. | |
3107 | @end deftypevr | |
3108 | ||
3109 | @comment fcntl.h | |
3110 | @comment BSD | |
3111 | @deftypevr Macro int O_EXLOCK | |
3112 | Acquire an exclusive lock on the file, as with @code{flock}. | |
3113 | @xref{File Locks}. This is atomic like @code{O_SHLOCK}. | |
3114 | @end deftypevr | |
3115 | ||
3116 | @node Operating Modes | |
3117 | @subsection I/O Operating Modes | |
3118 | ||
3119 | The operating modes affect how input and output operations using a file | |
3120 | descriptor work. These flags are set by @code{open} and can be fetched | |
3121 | and changed with @code{fcntl}. | |
3122 | ||
3123 | @comment fcntl.h | |
3124 | @comment POSIX.1 | |
3125 | @deftypevr Macro int O_APPEND | |
3126 | The bit that enables append mode for the file. If set, then all | |
3127 | @code{write} operations write the data at the end of the file, extending | |
3128 | it, regardless of the current file position. This is the only reliable | |
3129 | way to append to a file. In append mode, you are guaranteed that the | |
3130 | data you write will always go to the current end of the file, regardless | |
3131 | of other processes writing to the file. Conversely, if you simply set | |
3132 | the file position to the end of file and write, then another process can | |
3133 | extend the file after you set the file position but before you write, | |
3134 | resulting in your data appearing someplace before the real end of file. | |
3135 | @end deftypevr | |
3136 | ||
3137 | @comment fcntl.h | |
3138 | @comment POSIX.1 | |
2c6fe0bd | 3139 | @deftypevr Macro int O_NONBLOCK |
28f540f4 RM |
3140 | The bit that enables nonblocking mode for the file. If this bit is set, |
3141 | @code{read} requests on the file can return immediately with a failure | |
3142 | status if there is no input immediately available, instead of blocking. | |
3143 | Likewise, @code{write} requests can also return immediately with a | |
3144 | failure status if the output can't be written immediately. | |
3145 | ||
3146 | Note that the @code{O_NONBLOCK} flag is overloaded as both an I/O | |
3147 | operating mode and a file name translation flag; @pxref{Open-time Flags}. | |
3148 | @end deftypevr | |
3149 | ||
3150 | @comment fcntl.h | |
3151 | @comment BSD | |
3152 | @deftypevr Macro int O_NDELAY | |
3153 | This is an obsolete name for @code{O_NONBLOCK}, provided for | |
3154 | compatibility with BSD. It is not defined by the POSIX.1 standard. | |
3155 | @end deftypevr | |
3156 | ||
3157 | The remaining operating modes are BSD and GNU extensions. They exist only | |
3158 | on some systems. On other systems, these macros are not defined. | |
3159 | ||
3160 | @comment fcntl.h | |
3161 | @comment BSD | |
3162 | @deftypevr Macro int O_ASYNC | |
3163 | The bit that enables asynchronous input mode. If set, then @code{SIGIO} | |
3164 | signals will be generated when input is available. @xref{Interrupt Input}. | |
3165 | ||
3166 | Asynchronous input mode is a BSD feature. | |
3167 | @end deftypevr | |
3168 | ||
3169 | @comment fcntl.h | |
3170 | @comment BSD | |
3171 | @deftypevr Macro int O_FSYNC | |
3172 | The bit that enables synchronous writing for the file. If set, each | |
3173 | @code{write} call will make sure the data is reliably stored on disk before | |
3174 | returning. @c !!! xref fsync | |
3175 | ||
3176 | Synchronous writing is a BSD feature. | |
3177 | @end deftypevr | |
3178 | ||
3179 | @comment fcntl.h | |
3180 | @comment BSD | |
3181 | @deftypevr Macro int O_SYNC | |
3182 | This is another name for @code{O_FSYNC}. They have the same value. | |
3183 | @end deftypevr | |
3184 | ||
3185 | @comment fcntl.h | |
3186 | @comment GNU | |
3187 | @deftypevr Macro int O_NOATIME | |
3188 | If this bit is set, @code{read} will not update the access time of the | |
3189 | file. @xref{File Times}. This is used by programs that do backups, so | |
3190 | that backing a file up does not count as reading it. | |
3191 | Only the owner of the file or the superuser may use this bit. | |
3192 | ||
3193 | This is a GNU extension. | |
3194 | @end deftypevr | |
3195 | ||
3196 | @node Getting File Status Flags | |
3197 | @subsection Getting and Setting File Status Flags | |
3198 | ||
3199 | The @code{fcntl} function can fetch or change file status flags. | |
3200 | ||
3201 | @comment fcntl.h | |
3202 | @comment POSIX.1 | |
3203 | @deftypevr Macro int F_GETFL | |
3204 | This macro is used as the @var{command} argument to @code{fcntl}, to | |
3205 | read the file status flags for the open file with descriptor | |
3206 | @var{filedes}. | |
3207 | ||
3208 | The normal return value from @code{fcntl} with this command is a | |
3209 | nonnegative number which can be interpreted as the bitwise OR of the | |
3210 | individual flags. Since the file access modes are not single-bit values, | |
3211 | you can mask off other bits in the returned flags with @code{O_ACCMODE} | |
3212 | to compare them. | |
3213 | ||
07435eb4 | 3214 | In case of an error, @code{fcntl} returns @math{-1}. The following |
28f540f4 RM |
3215 | @code{errno} error conditions are defined for this command: |
3216 | ||
3217 | @table @code | |
3218 | @item EBADF | |
3219 | The @var{filedes} argument is invalid. | |
3220 | @end table | |
3221 | @end deftypevr | |
3222 | ||
3223 | @comment fcntl.h | |
3224 | @comment POSIX.1 | |
3225 | @deftypevr Macro int F_SETFL | |
3226 | This macro is used as the @var{command} argument to @code{fcntl}, to set | |
3227 | the file status flags for the open file corresponding to the | |
3228 | @var{filedes} argument. This command requires a third @code{int} | |
3229 | argument to specify the new flags, so the call looks like this: | |
3230 | ||
3231 | @smallexample | |
3232 | fcntl (@var{filedes}, F_SETFL, @var{new-flags}) | |
3233 | @end smallexample | |
3234 | ||
3235 | You can't change the access mode for the file in this way; that is, | |
3236 | whether the file descriptor was opened for reading or writing. | |
3237 | ||
3238 | The normal return value from @code{fcntl} with this command is an | |
07435eb4 | 3239 | unspecified value other than @math{-1}, which indicates an error. The |
28f540f4 RM |
3240 | error conditions are the same as for the @code{F_GETFL} command. |
3241 | @end deftypevr | |
3242 | ||
3243 | If you want to modify the file status flags, you should get the current | |
3244 | flags with @code{F_GETFL} and modify the value. Don't assume that the | |
3245 | flags listed here are the only ones that are implemented; your program | |
3246 | may be run years from now and more flags may exist then. For example, | |
3247 | here is a function to set or clear the flag @code{O_NONBLOCK} without | |
3248 | altering any other flags: | |
3249 | ||
3250 | @smallexample | |
3251 | @group | |
3252 | /* @r{Set the @code{O_NONBLOCK} flag of @var{desc} if @var{value} is nonzero,} | |
3253 | @r{or clear the flag if @var{value} is 0.} | |
2c6fe0bd | 3254 | @r{Return 0 on success, or -1 on error with @code{errno} set.} */ |
28f540f4 RM |
3255 | |
3256 | int | |
3257 | set_nonblock_flag (int desc, int value) | |
3258 | @{ | |
3259 | int oldflags = fcntl (desc, F_GETFL, 0); | |
3260 | /* @r{If reading the flags failed, return error indication now.} */ | |
3261 | if (oldflags == -1) | |
3262 | return -1; | |
3263 | /* @r{Set just the flag we want to set.} */ | |
3264 | if (value != 0) | |
3265 | oldflags |= O_NONBLOCK; | |
3266 | else | |
3267 | oldflags &= ~O_NONBLOCK; | |
3268 | /* @r{Store modified flag word in the descriptor.} */ | |
3269 | return fcntl (desc, F_SETFL, oldflags); | |
3270 | @} | |
3271 | @end group | |
3272 | @end smallexample | |
3273 | ||
3274 | @node File Locks | |
3275 | @section File Locks | |
3276 | ||
3277 | @cindex file locks | |
3278 | @cindex record locking | |
3279 | The remaining @code{fcntl} commands are used to support @dfn{record | |
3280 | locking}, which permits multiple cooperating programs to prevent each | |
3281 | other from simultaneously accessing parts of a file in error-prone | |
3282 | ways. | |
3283 | ||
3284 | @cindex exclusive lock | |
3285 | @cindex write lock | |
3286 | An @dfn{exclusive} or @dfn{write} lock gives a process exclusive access | |
3287 | for writing to the specified part of the file. While a write lock is in | |
3288 | place, no other process can lock that part of the file. | |
3289 | ||
3290 | @cindex shared lock | |
3291 | @cindex read lock | |
3292 | A @dfn{shared} or @dfn{read} lock prohibits any other process from | |
3293 | requesting a write lock on the specified part of the file. However, | |
3294 | other processes can request read locks. | |
3295 | ||
3296 | The @code{read} and @code{write} functions do not actually check to see | |
3297 | whether there are any locks in place. If you want to implement a | |
3298 | locking protocol for a file shared by multiple processes, your application | |
3299 | must do explicit @code{fcntl} calls to request and clear locks at the | |
3300 | appropriate points. | |
3301 | ||
3302 | Locks are associated with processes. A process can only have one kind | |
3303 | of lock set for each byte of a given file. When any file descriptor for | |
3304 | that file is closed by the process, all of the locks that process holds | |
3305 | on that file are released, even if the locks were made using other | |
3306 | descriptors that remain open. Likewise, locks are released when a | |
3307 | process exits, and are not inherited by child processes created using | |
3308 | @code{fork} (@pxref{Creating a Process}). | |
3309 | ||
3310 | When making a lock, use a @code{struct flock} to specify what kind of | |
3311 | lock and where. This data type and the associated macros for the | |
3312 | @code{fcntl} function are declared in the header file @file{fcntl.h}. | |
3313 | @pindex fcntl.h | |
3314 | ||
3315 | @comment fcntl.h | |
3316 | @comment POSIX.1 | |
3317 | @deftp {Data Type} {struct flock} | |
3318 | This structure is used with the @code{fcntl} function to describe a file | |
3319 | lock. It has these members: | |
3320 | ||
3321 | @table @code | |
3322 | @item short int l_type | |
3323 | Specifies the type of the lock; one of @code{F_RDLCK}, @code{F_WRLCK}, or | |
3324 | @code{F_UNLCK}. | |
3325 | ||
3326 | @item short int l_whence | |
3327 | This corresponds to the @var{whence} argument to @code{fseek} or | |
3328 | @code{lseek}, and specifies what the offset is relative to. Its value | |
3329 | can be one of @code{SEEK_SET}, @code{SEEK_CUR}, or @code{SEEK_END}. | |
3330 | ||
3331 | @item off_t l_start | |
3332 | This specifies the offset of the start of the region to which the lock | |
3333 | applies, and is given in bytes relative to the point specified by | |
3334 | @code{l_whence} member. | |
3335 | ||
3336 | @item off_t l_len | |
3337 | This specifies the length of the region to be locked. A value of | |
3338 | @code{0} is treated specially; it means the region extends to the end of | |
3339 | the file. | |
3340 | ||
3341 | @item pid_t l_pid | |
3342 | This field is the process ID (@pxref{Process Creation Concepts}) of the | |
3343 | process holding the lock. It is filled in by calling @code{fcntl} with | |
3344 | the @code{F_GETLK} command, but is ignored when making a lock. | |
3345 | @end table | |
3346 | @end deftp | |
3347 | ||
3348 | @comment fcntl.h | |
3349 | @comment POSIX.1 | |
3350 | @deftypevr Macro int F_GETLK | |
3351 | This macro is used as the @var{command} argument to @code{fcntl}, to | |
3352 | specify that it should get information about a lock. This command | |
3353 | requires a third argument of type @w{@code{struct flock *}} to be passed | |
3354 | to @code{fcntl}, so that the form of the call is: | |
3355 | ||
3356 | @smallexample | |
3357 | fcntl (@var{filedes}, F_GETLK, @var{lockp}) | |
3358 | @end smallexample | |
3359 | ||
3360 | If there is a lock already in place that would block the lock described | |
3361 | by the @var{lockp} argument, information about that lock overwrites | |
3362 | @code{*@var{lockp}}. Existing locks are not reported if they are | |
3363 | compatible with making a new lock as specified. Thus, you should | |
3364 | specify a lock type of @code{F_WRLCK} if you want to find out about both | |
3365 | read and write locks, or @code{F_RDLCK} if you want to find out about | |
3366 | write locks only. | |
3367 | ||
3368 | There might be more than one lock affecting the region specified by the | |
3369 | @var{lockp} argument, but @code{fcntl} only returns information about | |
3370 | one of them. The @code{l_whence} member of the @var{lockp} structure is | |
3371 | set to @code{SEEK_SET} and the @code{l_start} and @code{l_len} fields | |
3372 | set to identify the locked region. | |
3373 | ||
3374 | If no lock applies, the only change to the @var{lockp} structure is to | |
3375 | update the @code{l_type} to a value of @code{F_UNLCK}. | |
3376 | ||
3377 | The normal return value from @code{fcntl} with this command is an | |
07435eb4 | 3378 | unspecified value other than @math{-1}, which is reserved to indicate an |
28f540f4 RM |
3379 | error. The following @code{errno} error conditions are defined for |
3380 | this command: | |
3381 | ||
3382 | @table @code | |
3383 | @item EBADF | |
3384 | The @var{filedes} argument is invalid. | |
3385 | ||
3386 | @item EINVAL | |
3387 | Either the @var{lockp} argument doesn't specify valid lock information, | |
3388 | or the file associated with @var{filedes} doesn't support locks. | |
3389 | @end table | |
3390 | @end deftypevr | |
3391 | ||
3392 | @comment fcntl.h | |
3393 | @comment POSIX.1 | |
3394 | @deftypevr Macro int F_SETLK | |
3395 | This macro is used as the @var{command} argument to @code{fcntl}, to | |
3396 | specify that it should set or clear a lock. This command requires a | |
3397 | third argument of type @w{@code{struct flock *}} to be passed to | |
3398 | @code{fcntl}, so that the form of the call is: | |
3399 | ||
3400 | @smallexample | |
3401 | fcntl (@var{filedes}, F_SETLK, @var{lockp}) | |
3402 | @end smallexample | |
3403 | ||
3404 | If the process already has a lock on any part of the region, the old lock | |
3405 | on that part is replaced with the new lock. You can remove a lock | |
3406 | by specifying a lock type of @code{F_UNLCK}. | |
3407 | ||
3408 | If the lock cannot be set, @code{fcntl} returns immediately with a value | |
07435eb4 | 3409 | of @math{-1}. This function does not block waiting for other processes |
28f540f4 | 3410 | to release locks. If @code{fcntl} succeeds, it return a value other |
07435eb4 | 3411 | than @math{-1}. |
28f540f4 RM |
3412 | |
3413 | The following @code{errno} error conditions are defined for this | |
3414 | function: | |
3415 | ||
3416 | @table @code | |
3417 | @item EAGAIN | |
3418 | @itemx EACCES | |
3419 | The lock cannot be set because it is blocked by an existing lock on the | |
3420 | file. Some systems use @code{EAGAIN} in this case, and other systems | |
3421 | use @code{EACCES}; your program should treat them alike, after | |
a7a93d50 | 3422 | @code{F_SETLK}. (@gnulinuxhurdsystems{} always use @code{EAGAIN}.) |
28f540f4 RM |
3423 | |
3424 | @item EBADF | |
3425 | Either: the @var{filedes} argument is invalid; you requested a read lock | |
3426 | but the @var{filedes} is not open for read access; or, you requested a | |
3427 | write lock but the @var{filedes} is not open for write access. | |
3428 | ||
3429 | @item EINVAL | |
3430 | Either the @var{lockp} argument doesn't specify valid lock information, | |
3431 | or the file associated with @var{filedes} doesn't support locks. | |
3432 | ||
3433 | @item ENOLCK | |
3434 | The system has run out of file lock resources; there are already too | |
3435 | many file locks in place. | |
3436 | ||
3437 | Well-designed file systems never report this error, because they have no | |
3438 | limitation on the number of locks. However, you must still take account | |
3439 | of the possibility of this error, as it could result from network access | |
3440 | to a file system on another machine. | |
3441 | @end table | |
3442 | @end deftypevr | |
3443 | ||
3444 | @comment fcntl.h | |
3445 | @comment POSIX.1 | |
3446 | @deftypevr Macro int F_SETLKW | |
3447 | This macro is used as the @var{command} argument to @code{fcntl}, to | |
3448 | specify that it should set or clear a lock. It is just like the | |
3449 | @code{F_SETLK} command, but causes the process to block (or wait) | |
3450 | until the request can be specified. | |
3451 | ||
3452 | This command requires a third argument of type @code{struct flock *}, as | |
3453 | for the @code{F_SETLK} command. | |
3454 | ||
3455 | The @code{fcntl} return values and errors are the same as for the | |
3456 | @code{F_SETLK} command, but these additional @code{errno} error conditions | |
3457 | are defined for this command: | |
3458 | ||
3459 | @table @code | |
3460 | @item EINTR | |
3461 | The function was interrupted by a signal while it was waiting. | |
3462 | @xref{Interrupted Primitives}. | |
3463 | ||
3464 | @item EDEADLK | |
3465 | The specified region is being locked by another process. But that | |
3466 | process is waiting to lock a region which the current process has | |
3467 | locked, so waiting for the lock would result in deadlock. The system | |
3468 | does not guarantee that it will detect all such conditions, but it lets | |
3469 | you know if it notices one. | |
3470 | @end table | |
3471 | @end deftypevr | |
3472 | ||
3473 | ||
3474 | The following macros are defined for use as values for the @code{l_type} | |
3475 | member of the @code{flock} structure. The values are integer constants. | |
3476 | ||
3477 | @table @code | |
3478 | @comment fcntl.h | |
3479 | @comment POSIX.1 | |
3480 | @vindex F_RDLCK | |
3481 | @item F_RDLCK | |
3482 | This macro is used to specify a read (or shared) lock. | |
3483 | ||
3484 | @comment fcntl.h | |
3485 | @comment POSIX.1 | |
3486 | @vindex F_WRLCK | |
3487 | @item F_WRLCK | |
3488 | This macro is used to specify a write (or exclusive) lock. | |
3489 | ||
3490 | @comment fcntl.h | |
3491 | @comment POSIX.1 | |
3492 | @vindex F_UNLCK | |
3493 | @item F_UNLCK | |
3494 | This macro is used to specify that the region is unlocked. | |
3495 | @end table | |
3496 | ||
3497 | As an example of a situation where file locking is useful, consider a | |
3498 | program that can be run simultaneously by several different users, that | |
3499 | logs status information to a common file. One example of such a program | |
3500 | might be a game that uses a file to keep track of high scores. Another | |
3501 | example might be a program that records usage or accounting information | |
3502 | for billing purposes. | |
3503 | ||
3504 | Having multiple copies of the program simultaneously writing to the | |
3505 | file could cause the contents of the file to become mixed up. But | |
3506 | you can prevent this kind of problem by setting a write lock on the | |
2c6fe0bd | 3507 | file before actually writing to the file. |
28f540f4 RM |
3508 | |
3509 | If the program also needs to read the file and wants to make sure that | |
3510 | the contents of the file are in a consistent state, then it can also use | |
3511 | a read lock. While the read lock is set, no other process can lock | |
3512 | that part of the file for writing. | |
3513 | ||
3514 | @c ??? This section could use an example program. | |
3515 | ||
3516 | Remember that file locks are only a @emph{voluntary} protocol for | |
3517 | controlling access to a file. There is still potential for access to | |
3518 | the file by programs that don't use the lock protocol. | |
3519 | ||
3520 | @node Interrupt Input | |
3521 | @section Interrupt-Driven Input | |
3522 | ||
3523 | @cindex interrupt-driven input | |
3524 | If you set the @code{O_ASYNC} status flag on a file descriptor | |
3525 | (@pxref{File Status Flags}), a @code{SIGIO} signal is sent whenever | |
3526 | input or output becomes possible on that file descriptor. The process | |
3527 | or process group to receive the signal can be selected by using the | |
3528 | @code{F_SETOWN} command to the @code{fcntl} function. If the file | |
3529 | descriptor is a socket, this also selects the recipient of @code{SIGURG} | |
3530 | signals that are delivered when out-of-band data arrives on that socket; | |
3531 | see @ref{Out-of-Band Data}. (@code{SIGURG} is sent in any situation | |
3532 | where @code{select} would report the socket as having an ``exceptional | |
3533 | condition''. @xref{Waiting for I/O}.) | |
3534 | ||
3535 | If the file descriptor corresponds to a terminal device, then @code{SIGIO} | |
2c6fe0bd | 3536 | signals are sent to the foreground process group of the terminal. |
28f540f4 RM |
3537 | @xref{Job Control}. |
3538 | ||
3539 | @pindex fcntl.h | |
3540 | The symbols in this section are defined in the header file | |
3541 | @file{fcntl.h}. | |
3542 | ||
3543 | @comment fcntl.h | |
3544 | @comment BSD | |
3545 | @deftypevr Macro int F_GETOWN | |
3546 | This macro is used as the @var{command} argument to @code{fcntl}, to | |
3547 | specify that it should get information about the process or process | |
3548 | group to which @code{SIGIO} signals are sent. (For a terminal, this is | |
3549 | actually the foreground process group ID, which you can get using | |
3550 | @code{tcgetpgrp}; see @ref{Terminal Access Functions}.) | |
3551 | ||
3552 | The return value is interpreted as a process ID; if negative, its | |
3553 | absolute value is the process group ID. | |
3554 | ||
3555 | The following @code{errno} error condition is defined for this command: | |
3556 | ||
3557 | @table @code | |
3558 | @item EBADF | |
3559 | The @var{filedes} argument is invalid. | |
3560 | @end table | |
3561 | @end deftypevr | |
3562 | ||
3563 | @comment fcntl.h | |
3564 | @comment BSD | |
3565 | @deftypevr Macro int F_SETOWN | |
3566 | This macro is used as the @var{command} argument to @code{fcntl}, to | |
3567 | specify that it should set the process or process group to which | |
3568 | @code{SIGIO} signals are sent. This command requires a third argument | |
3569 | of type @code{pid_t} to be passed to @code{fcntl}, so that the form of | |
3570 | the call is: | |
3571 | ||
3572 | @smallexample | |
3573 | fcntl (@var{filedes}, F_SETOWN, @var{pid}) | |
3574 | @end smallexample | |
3575 | ||
3576 | The @var{pid} argument should be a process ID. You can also pass a | |
3577 | negative number whose absolute value is a process group ID. | |
3578 | ||
07435eb4 | 3579 | The return value from @code{fcntl} with this command is @math{-1} |
28f540f4 RM |
3580 | in case of error and some other value if successful. The following |
3581 | @code{errno} error conditions are defined for this command: | |
3582 | ||
3583 | @table @code | |
3584 | @item EBADF | |
3585 | The @var{filedes} argument is invalid. | |
3586 | ||
3587 | @item ESRCH | |
3588 | There is no process or process group corresponding to @var{pid}. | |
3589 | @end table | |
3590 | @end deftypevr | |
3591 | ||
3592 | @c ??? This section could use an example program. | |
07435eb4 UD |
3593 | |
3594 | @node IOCTLs | |
3595 | @section Generic I/O Control operations | |
3596 | @cindex generic i/o control operations | |
3597 | @cindex IOCTLs | |
3598 | ||
a7a93d50 | 3599 | @gnusystems{} can handle most input/output operations on many different |
07435eb4 UD |
3600 | devices and objects in terms of a few file primitives - @code{read}, |
3601 | @code{write} and @code{lseek}. However, most devices also have a few | |
3602 | peculiar operations which do not fit into this model. Such as: | |
3603 | ||
3604 | @itemize @bullet | |
3605 | ||
3606 | @item | |
3607 | Changing the character font used on a terminal. | |
3608 | ||
3609 | @item | |
3610 | Telling a magnetic tape system to rewind or fast forward. (Since they | |
3611 | cannot move in byte increments, @code{lseek} is inapplicable). | |
3612 | ||
3613 | @item | |
3614 | Ejecting a disk from a drive. | |
3615 | ||
3616 | @item | |
3617 | Playing an audio track from a CD-ROM drive. | |
3618 | ||
3619 | @item | |
3620 | Maintaining routing tables for a network. | |
3621 | ||
3622 | @end itemize | |
3623 | ||
3624 | Although some such objects such as sockets and terminals | |
3625 | @footnote{Actually, the terminal-specific functions are implemented with | |
3626 | IOCTLs on many platforms.} have special functions of their own, it would | |
3627 | not be practical to create functions for all these cases. | |
3628 | ||
3629 | Instead these minor operations, known as @dfn{IOCTL}s, are assigned code | |
3630 | numbers and multiplexed through the @code{ioctl} function, defined in | |
3631 | @code{sys/ioctl.h}. The code numbers themselves are defined in many | |
3632 | different headers. | |
3633 | ||
b2e3d177 UD |
3634 | @comment sys/ioctl.h |
3635 | @comment BSD | |
07435eb4 UD |
3636 | @deftypefun int ioctl (int @var{filedes}, int @var{command}, @dots{}) |
3637 | ||
3638 | The @code{ioctl} function performs the generic I/O operation | |
3639 | @var{command} on @var{filedes}. | |
3640 | ||
3641 | A third argument is usually present, either a single number or a pointer | |
3642 | to a structure. The meaning of this argument, the returned value, and | |
3643 | any error codes depends upon the command used. Often @math{-1} is | |
3644 | returned for a failure. | |
3645 | ||
3646 | @end deftypefun | |
3647 | ||
3648 | On some systems, IOCTLs used by different devices share the same numbers. | |
3649 | Thus, although use of an inappropriate IOCTL @emph{usually} only produces | |
3650 | an error, you should not attempt to use device-specific IOCTLs on an | |
3651 | unknown device. | |
3652 | ||
3653 | Most IOCTLs are OS-specific and/or only used in special system utilities, | |
3654 | and are thus beyond the scope of this document. For an example of the use | |
8b7fb588 | 3655 | of an IOCTL, see @ref{Out-of-Band Data}. |