[iptables PATCH 3/5] man: ebtables-nft.8: Note that --concurrent is a NOP

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

 



For obvious reasons, ebtables-nft does not need file-based locking to
prevent concurrency.

Fixes: 1939cbc25e6f5 ("doc: Adjust ebtables man page")
Signed-off-by: Phil Sutter <phil@xxxxxx>
---
 iptables/ebtables-nft.8 | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/iptables/ebtables-nft.8 b/iptables/ebtables-nft.8
index 29c7d9faf8106..8698165024de1 100644
--- a/iptables/ebtables-nft.8
+++ b/iptables/ebtables-nft.8
@@ -358,7 +358,8 @@ When talking to the kernel, use this
 to try to automatically load missing kernel modules.
 .TP
 .B --concurrent
-Use a file lock to support concurrent scripts updating the ebtables kernel tables.
+This would use a file lock to support concurrent scripts updating the ebtables
+kernel tables. It is not needed with \fBebtables-nft\fP though and thus ignored.
 
 .SS
 RULE SPECIFICATIONS
-- 
2.43.0





[Index of Archives]     [Netfitler Users]     [Berkeley Packet Filter]     [LARTC]     [Bugtraq]     [Yosemite Forum]

  Powered by Linux