diff options
| author | Ian Turner <iturner@janestreet.com> | 2018-11-01 14:44:35 -0400 |
|---|---|---|
| committer | Michael Kerrisk <mtk.manpages@gmail.com> | 2018-11-02 07:47:39 +0100 |
| commit | 9e8d7a89254378b2a50a5011126ecd726474267c (patch) | |
| tree | 6ef10a5f31391a4ae279073d85c73e4830c10692 /man3 | |
| parent | 3bcfaff627cdc2dba5211941b130b6431c17453b (diff) | |
| download | man-pages-9e8d7a89254378b2a50a5011126ecd726474267c.tar.gz | |
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>
Diffstat (limited to 'man3')
| -rw-r--r-- | man3/lockf.3 | 5 |
1 files changed, 5 insertions, 0 deletions
diff --git a/man3/lockf.3 b/man3/lockf.3 index 80ce61f65f..f83ae3b056 100644 --- a/man3/lockf.3 +++ b/man3/lockf.3 @@ -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 . |