mirror of https://github.com/mkerrisk/man-pages
fork.2, read.2, sendfile.2, splice.2, write.2, aio_read.3, aio_write.3, proc.5: Wording fix: "current file offset" ==> "file offset"
"File offset" is the preferred POSIX terminology. Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
This commit is contained in:
parent
f180e30bc2
commit
c72249c562
|
@ -175,7 +175,7 @@ open file description (see
|
|||
.BR open (2))
|
||||
as the corresponding file descriptor in the parent.
|
||||
This means that the two file descriptors share open file status flags,
|
||||
current file offset,
|
||||
file offset,
|
||||
and signal-driven I/O attributes (see the description of
|
||||
.B F_SETOWN
|
||||
and
|
||||
|
|
|
@ -51,9 +51,9 @@ into the buffer starting at
|
|||
.IR buf .
|
||||
|
||||
On files that support seeking,
|
||||
the read operation commences at the current file offset,
|
||||
the read operation commences at the file offset,
|
||||
and the file offset is incremented by the number of bytes read.
|
||||
If the current file offset is at or past the end of file,
|
||||
If the file offset is at or past the end of file,
|
||||
no bytes are read, and
|
||||
.BR read ()
|
||||
returns zero.
|
||||
|
@ -140,7 +140,7 @@ flag, and either the address specified in
|
|||
.IR buf ,
|
||||
the value specified in
|
||||
.IR count ,
|
||||
or the current file offset is not suitably aligned.
|
||||
or the file offset is not suitably aligned.
|
||||
.TP
|
||||
.B EINVAL
|
||||
.I fd
|
||||
|
|
|
@ -75,9 +75,9 @@ If
|
|||
.I offset
|
||||
is not NULL, then
|
||||
.BR sendfile ()
|
||||
does not modify the current file offset of
|
||||
does not modify the file offset of
|
||||
.IR in_fd ;
|
||||
otherwise the current file offset is adjusted to reflect
|
||||
otherwise the file offset is adjusted to reflect
|
||||
the number of bytes read from
|
||||
.IR in_fd .
|
||||
|
||||
|
@ -85,7 +85,7 @@ If
|
|||
.I offset
|
||||
is NULL, then data will be read from
|
||||
.IR in_fd
|
||||
starting at the current file offset,
|
||||
starting at the file offset,
|
||||
and the file offset will be updated by the call.
|
||||
|
||||
.I count
|
||||
|
|
|
@ -65,8 +65,8 @@ does not refer to a pipe and
|
|||
.I off_in
|
||||
is NULL, then bytes are read from
|
||||
.I fd_in
|
||||
starting from the current file offset,
|
||||
and the current file offset is adjusted appropriately.
|
||||
starting from the file offset,
|
||||
and the file offset is adjusted appropriately.
|
||||
.IP *
|
||||
If
|
||||
.I fd_in
|
||||
|
@ -77,7 +77,7 @@ is not NULL, then
|
|||
must point to a buffer which specifies the starting
|
||||
offset from which bytes will be read from
|
||||
.IR fd_in ;
|
||||
in this case, the current file offset of
|
||||
in this case, the file offset of
|
||||
.I fd_in
|
||||
is not changed.
|
||||
.PP
|
||||
|
|
|
@ -69,7 +69,7 @@ bytes.
|
|||
For a seekable file (i.e., one to which
|
||||
.BR lseek (2)
|
||||
may be applied, for example, a regular file)
|
||||
writing takes place at the current file offset,
|
||||
writing takes place at the file offset,
|
||||
and the file offset is incremented by
|
||||
the number of bytes actually written.
|
||||
If the file was
|
||||
|
@ -170,7 +170,7 @@ flag, and either the address specified in
|
|||
.IR buf ,
|
||||
the value specified in
|
||||
.IR count ,
|
||||
or the current file offset is not suitably aligned.
|
||||
or the file offset is not suitably aligned.
|
||||
.TP
|
||||
.B EIO
|
||||
A low-level I/O error occurred while modifying the inode.
|
||||
|
|
|
@ -54,11 +54,11 @@ for a description of the
|
|||
.I aiocb
|
||||
structure.)
|
||||
.LP
|
||||
The data is read starting at the absolute file offset
|
||||
The data is read starting at the absolute position
|
||||
.IR aiocbp\->aio_offset ,
|
||||
regardless of the current file offset.
|
||||
regardless of the file offset.
|
||||
After the call,
|
||||
the value of the current file offset is unspecified.
|
||||
the value of the file offset is unspecified.
|
||||
.LP
|
||||
The "asynchronous" means that this call returns as soon as the
|
||||
request has been enqueued; the read may or may not have completed
|
||||
|
|
|
@ -57,15 +57,15 @@ structure.)
|
|||
If
|
||||
.B O_APPEND
|
||||
is not set, the data is written starting at the
|
||||
absolute file offset
|
||||
absolute position
|
||||
.IR aiocbp\->aio_offset ,
|
||||
regardless of the current file offset.
|
||||
regardless of the file offset.
|
||||
If
|
||||
.B O_APPEND
|
||||
is set, data is written at the end of the file in the same order as
|
||||
.BR aio_write ()
|
||||
calls are made.
|
||||
After the call, the value of the current file offset is unspecified.
|
||||
After the call, the value of the file offset is unspecified.
|
||||
.LP
|
||||
The "asynchronous" means that this call returns as soon as the
|
||||
request has been enqueued; the write may or may not have completed
|
||||
|
|
|
@ -634,7 +634,7 @@ mnt_id: 21
|
|||
|
||||
The
|
||||
.I pos
|
||||
field is a decimal number showing the current file offset.
|
||||
field is a decimal number showing the file offset.
|
||||
The
|
||||
.I flags
|
||||
field is an octal number that displays the
|
||||
|
|
Loading…
Reference in New Issue