[PATCH] flock(1): Decribe limitations of flock: deadlock, NFS, CIFS

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



The flock(1) does not refer to limitations of flock(2). Provide an
documentation entry point for solving of problems with flock on NFS
and CIFS and mention risk of deadlock.

Signed-off-by: Stanislav Brabec <sbrabec@xxxxxxx>
---
 sys-utils/flock.1.adoc | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/sys-utils/flock.1.adoc b/sys-utils/flock.1.adoc
index c645a60f6..d5b4f10aa 100644
--- a/sys-utils/flock.1.adoc
+++ b/sys-utils/flock.1.adoc
@@ -91,6 +91,12 @@ The command uses <sysexits.h> exit status values for everything, except when usi
When using the _command_ variant, and executing the child worked, then the exit status is that of the child command. +== NOTES
+
+*flock* does not detect deadlock. See *flock*(2) for details.
+
+Some file systems (e. g. NFS and CIFS) have a limited implementation of *flock*(2) and flock may always fail. For details see *flock*(2), *nfs*(5) and *mount.cifs*(8). Depending on mount options, flock can always fail there.
+
 == EXAMPLES
Note that "shell> " in examples is a command line prompt.
--
2.35.1

--
Best Regards / S pozdravem,

Stanislav Brabec
software developer
---------------------------------------------------------------------
SUSE LINUX, s. r. o.                         e-mail: sbrabec@xxxxxxxx
Křižíkova 148/34 (Corso IIa)                    tel: +420 284 084 060
186 00 Praha 8-Karlín                          fax:  +420 284 084 001
Czech Republic                                    http://www.suse.cz/
PGP: 830B 40D5 9E05 35D8 5E27 6FA3 717C 209F A04F CD76



[Index of Archives]     [Netdev]     [Ethernet Bridging]     [Linux Wireless]     [Kernel Newbies]     [Security]     [Linux for Hams]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux Admin]     [Samba]

  Powered by Linux