From: Phil Sutter <phil@nwl.cc>
To: netfilter-devel@vger.kernel.org
Subject: [iptables PATCH 3/5] man: ebtables-nft.8: Note that --concurrent is a NOP
Date: Wed, 9 Oct 2024 12:50:35 +0200 [thread overview]
Message-ID: <20241009105037.30114-4-phil@nwl.cc> (raw)
In-Reply-To: <20241009105037.30114-1-phil@nwl.cc>
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@nwl.cc>
---
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
next prev parent reply other threads:[~2024-10-09 10:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-09 10:50 [iptables PATCH 0/5] Some minor fixes Phil Sutter
2024-10-09 10:50 ` [iptables PATCH 1/5] tests: iptables-test: Append stderr output to log file Phil Sutter
2024-10-09 10:50 ` [iptables PATCH 2/5] man: xtables-legacy.8: Join two paragraphs Phil Sutter
2024-10-09 10:50 ` Phil Sutter [this message]
2024-10-09 10:50 ` [iptables PATCH 4/5] gitignore: Ignore generated arptables-translate.8 Phil Sutter
2024-10-09 10:50 ` [iptables PATCH 5/5] xshared: iptables does not support '-b' Phil Sutter
2024-10-16 13:33 ` [iptables PATCH 0/5] Some minor fixes Phil Sutter
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20241009105037.30114-4-phil@nwl.cc \
--to=phil@nwl.cc \
--cc=netfilter-devel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).