mirror of https://github.com/mkerrisk/man-pages
lockf.3: ERRORS: add EINTR
Ian Turner: The exact return calls are at the discretion of the underlying VFS, but I'm pretty sure that EINTR is a possibility. Or, if it's not, then the flock() manpage should be amended accordingly, since the two share the same underlying implementation. mtk: lockf(3) is implemented on top of fcntl() locking, so EINTR is of course a possibility. Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
This commit is contained in:
parent
3bcfaff627
commit
9e8d7a8925
|
@ -147,6 +147,11 @@ The command was
|
|||
.B F_LOCK
|
||||
and this lock operation would cause a deadlock.
|
||||
.TP
|
||||
.B EINTR
|
||||
While waiting to acquire a lock, the call was interrupted by
|
||||
delivery of a signal caught by a handler; see
|
||||
.BR signal (7).
|
||||
.TP
|
||||
.B EINVAL
|
||||
An invalid operation was specified in
|
||||
.IR cmd .
|
||||
|
|
Loading…
Reference in New Issue