LDP
/
man-pages
mirror of https://github.com/mkerrisk/man-pages
0
1
Fork 0
Code Releases Activity

flock.2: Employ term "open file description" in DESCRIPTION 

And include reference to open(2) for an explanation of the term.

Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
This commit is contained in:
Michael Kerrisk 2014-04-22 10:00:07 +02:00
parent 04346be5bb
commit 61a37c81ef
1 changed files with 3 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
man2/flock.2
View File

@ -32,7 +32,7 @@
.\" FIXME: Maybe document LOCK_MAND, LOCK_RW, LOCK_READ, LOCK_WRITE
.\" which only have effect for SAMBA.
.\"
.TH FLOCK 2 2013-02-11 "Linux" "Linux Programmer's Manual"
.TH FLOCK 2 2014-04-22 "Linux" "Linux Programmer's Manual"
.SH NAME
flock \- apply or remove an advisory lock on an open file
.SH SYNOPSIS
@ -73,7 +73,8 @@ A single file may not simultaneously have both shared and exclusive locks.
Locks created by
.BR flock ()
are associated with an open file table entry.
are associated with an open file description (see
.BR open (2)).
This means that duplicate file descriptors (created by, for example,
.BR fork (2)
or