On Wednesday 2023-08-02 04:03, Phil Sutter wrote:
>- Consistently use 'modprobe' as option argument name
>- Add a reference to modprobe man page
>- Put the path in italics, and the command in bold
>
>Reported-by: debian@xxxxxxxxxxxxx
>Fixes: 8c46901ff5785 ("doc: document iptables-restore's -M option")
>Signed-off-by: Phil Sutter <phil@xxxxxx>
>---
> iptables/iptables-restore.8.in | 7 ++++---
> 1 file changed, 4 insertions(+), 3 deletions(-)
>
>diff --git a/iptables/iptables-restore.8.in b/iptables/iptables-restore.8.in
>index 20216842d8358..5846a47cefbcc 100644
>--- a/iptables/iptables-restore.8.in
>+++ b/iptables/iptables-restore.8.in
>@@ -67,9 +67,10 @@ the program will exit if the lock cannot be obtained. This option will
> make the program wait (indefinitely or for optional \fIseconds\fP) until
> the exclusive lock can be obtained.
> .TP
>-\fB\-M\fP, \fB\-\-modprobe\fP \fImodprobe_program\fP
>-Specify the path to the modprobe program. By default, iptables-restore will
>-inspect /proc/sys/kernel/modprobe to determine the executable's path.
>+\fB\-M\fP, \fB\-\-modprobe\fP \fImodprobe\fP
>+Specify the path to the \fBmodprobe\fP(8) program. By default,
>+\fBiptables-restore\fP will inspect \fI/proc/sys/kernel/modprobe\fP to
>+determine the executable's path.
Same \fB..\fP counterargument as for patch 6/16.
