lseek.2: Remove slightly bogus advice about race conditions

The page already (by now) contains a reference to open(2)
for a discussion of open file descriptions. Leave it at that,
since the reader can then deduce how things work.

Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
This commit is contained in:
Michael Kerrisk 2017-02-20 23:23:16 +01:00
parent c257d35f5b
commit f225d14b1b
1 changed files with 0 additions and 7 deletions

View File

@ -260,13 +260,6 @@ on a terminal device fails with the error
\fBESPIPE\fP.
.\" Other systems return the number of written characters,
.\" using SEEK_SET to set the counter. (Of written characters.)
.PP
Note that file descriptors created by
.BR dup (2)
or
.BR fork (2)
refer to the same open file descriptions (and thus file offsets),
so seeking on such files may be subject to race conditions.
.SH SEE ALSO
.BR dup (2),
.BR fork (2),