diff options
Diffstat (limited to 'upstream/debian-unstable/man2/read.2')
| -rw-r--r-- | upstream/debian-unstable/man2/read.2 | 22 |
1 files changed, 11 insertions, 11 deletions
diff --git a/upstream/debian-unstable/man2/read.2 b/upstream/debian-unstable/man2/read.2 index 955efa46..1a8cee49 100644 --- a/upstream/debian-unstable/man2/read.2 +++ b/upstream/debian-unstable/man2/read.2 @@ -13,7 +13,7 @@ .\" Modified Sat Jul 12 20:45:39 1997 by Michael Haardt .\" <michael@cantor.informatik.rwth-aachen.de> .\" -.TH read 2 2023-04-03 "Linux man-pages 6.05.01" +.TH read 2 2024-05-02 "Linux man-pages 6.8" .SH NAME read \- read from a file descriptor .SH LIBRARY @@ -22,7 +22,7 @@ Standard C library .SH SYNOPSIS .nf .B #include <unistd.h> -.PP +.P .BI "ssize_t read(int " fd ", void " buf [. count "], size_t " count ); .fi .SH DESCRIPTION @@ -33,7 +33,7 @@ bytes from file descriptor .I fd into the buffer starting at .IR buf . -.PP +.P On files that support seeking, the read operation commences at the file offset, and the file offset is incremented by the number of bytes read. @@ -41,7 +41,7 @@ If the file offset is at or past the end of file, no bytes are read, and .BR read () returns zero. -.PP +.P If .I count is zero, @@ -56,7 +56,7 @@ does not check for errors, a with a .I count of 0 returns zero and has no other effects. -.PP +.P According to POSIX.1, if .I count is greater than @@ -73,7 +73,7 @@ because we are reading from a pipe, or from a terminal), or because .BR read () was interrupted by a signal. See also NOTES. -.PP +.P On error, \-1 is returned, and .I errno is set to indicate the error. @@ -160,7 +160,7 @@ for further details. .B EISDIR .I fd refers to a directory. -.PP +.P Other errors may occur, depending on the object connected to .IR fd . .SH STANDARDS @@ -175,7 +175,7 @@ On Linux, returning the number of bytes actually transferred. .\" commit e28cc71572da38a5a12c1cfe4d7032017adccf69 (This is true on both 32-bit and 64-bit systems.) -.PP +.P On NFS filesystems, reading small amounts of data will update the timestamp only the first time, subsequent calls may not do so. This is caused @@ -194,13 +194,13 @@ increase server load and decrease performance. .SH BUGS According to POSIX.1-2008/SUSv4 Section XSI 2.9.7 ("Thread Interactions with Regular File Operations"): -.PP +.P .RS 4 All of the following functions shall be atomic with respect to each other in the effects specified in POSIX.1-2008 when they operate on regular files or symbolic links: ... .RE -.PP +.P Among the APIs subsequently listed are .BR read () and @@ -216,7 +216,7 @@ perform a (or .BR readv (2)) at the same time, then the I/O operations were not atomic -with respect updating the file offset, +with respect to updating the file offset, with the result that the reads in the two processes might (incorrectly) overlap in the blocks of data that they obtained. This problem was fixed in Linux 3.14. |