| Message ID | 20250307001034.3141833-1-bmarzins@redhat.com (mailing list archive) |
|---|---|
| State | New |
| Headers | show |
| Series | [1/2] multipath: clean up find_multipaths documentation | expand |
On Thu, 2025-03-06 at 19:10 -0500, Benjamin Marzinski wrote: > The preferred term is "on" instead of "yes". > > Signed-off-by: Benjamin Marzinski <bmarzins@redhat.com> Reviewed-by: Martin Wilck <mwilck@suse.com> > --- > multipath/multipath.conf.5.in | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/multipath/multipath.conf.5.in > b/multipath/multipath.conf.5.in > index 0c1eff40..bdb6b605 100644 > --- a/multipath/multipath.conf.5.in > +++ b/multipath/multipath.conf.5.in > @@ -1214,7 +1214,7 @@ Both multipathd and multipath treat every non- > blacklisted device as multipath > device path. > .TP > .I smart > -This differs from \fIfind_multipaths yes\fR only in > +This differs from \fIfind_multipaths on\fR only in > the way it treats new devices for which only one path has been > detected yet. When such a device is first encountered in udev rules, > it is > treated as a multipath device. multipathd waits whether additional > paths with
diff --git a/multipath/multipath.conf.5.in b/multipath/multipath.conf.5.in index 0c1eff40..bdb6b605 100644 --- a/multipath/multipath.conf.5.in +++ b/multipath/multipath.conf.5.in @@ -1214,7 +1214,7 @@ Both multipathd and multipath treat every non-blacklisted device as multipath device path. .TP .I smart -This differs from \fIfind_multipaths yes\fR only in +This differs from \fIfind_multipaths on\fR only in the way it treats new devices for which only one path has been detected yet. When such a device is first encountered in udev rules, it is treated as a multipath device. multipathd waits whether additional paths with
The preferred term is "on" instead of "yes". Signed-off-by: Benjamin Marzinski <bmarzins@redhat.com> --- multipath/multipath.conf.5.in | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)