From 61a37c81ef11da9a12df91da181b943ef29cf2ba Mon Sep 17 00:00:00 2001 From: Michael Kerrisk Date: Tue, 22 Apr 2014 10:00:07 +0200 Subject: [PATCH] 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 --- man2/flock.2 | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/man2/flock.2 b/man2/flock.2 index 838cc7e26..324f37d1f 100644 --- a/man2/flock.2 +++ b/man2/flock.2 @@ -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