From 703251401cb11ee5d00a6b8f8bd9dc80c160f476 Mon Sep 17 00:00:00 2001
From: Terry Burton
Date: Thu, 14 Apr 2016 12:27:52 +0100
Subject: flock: Introduce no-fork option.

When guarding a command with flock it is sometimes preferable to not leave a
flock process waiting around for the command to exit.
---
 sys-utils/flock.1 | 8 ++++++++
 1 file changed, 8 insertions(+)

(limited to 'sys-utils/flock.1')

diff --git a/sys-utils/flock.1 b/sys-utils/flock.1
index 8e9d5c29a..c10cde5ff 100644
--- a/sys-utils/flock.1
+++ b/sys-utils/flock.1
@@ -70,6 +70,14 @@ The exit code used when the \fB\-n\fP option is in use, and the
 conflicting lock exists, or the \fB\-w\fP option is in use,
 and the timeout is reached.  The default value is \fB1\fR.
 .TP
+.BR \-F , " \-\-no\-fork"
+Do not fork before executing
+.IR command .
+Upon execution the flock process is replaced by
+.IR command
+which continues to hold the lock. This option is incompatible with
+\fB\-\-close\fR as there would otherwise be nothing left to hold the lock.
+.TP
 .BR \-e , " \-x" , " \-\-exclusive"
 Obtain an exclusive lock, sometimes called a write lock.  This is the
 default.
-- 
cgit v1.2.3-55-g7522