Add "If enabled, " to the sentence about multipathd.socket, since it is no longer enabled by default.
Signed-off-by: Benjamin Marzinski <[email protected]> --- multipathd/multipathd.8.in | 13 +++++++------ 1 file changed, 7 insertions(+), 6 deletions(-) diff --git a/multipathd/multipathd.8.in b/multipathd/multipathd.8.in index 12b77156..06d91c06 100644 --- a/multipathd/multipathd.8.in +++ b/multipathd/multipathd.8.in @@ -339,12 +339,13 @@ Stop multipathd. .\" ---------------------------------------------------------------------------- . When compiled with systemd support two systemd service files are installed, -\fImultipathd.service\fR and \fImultipathd.socket\fR The \fImultipathd.socket\fR -service instructs systemd to intercept the CLI command socket, so that any call -to the CLI interface will start-up the daemon if required. -The \fImultipathd.service\fR file carries the definitions for controlling the -multipath daemon. The daemon itself uses the \fBsd_notify\fR(3) interface to -communicate with systemd. The following unit keywords are recognized: +\fImultipathd.service\fR and \fImultipathd.socket\fR. If enabled, the +\fImultipathd.socket\fR service instructs systemd to intercept the CLI command +socket, so that any call to the CLI interface will start-up the daemon if +required. The \fImultipathd.service\fR file carries the definitions for +controlling the multipath daemon. The daemon itself uses the \fBsd_notify\fR(3) +interface to communicate with systemd. The following unit keywords are +recognized: . .TP .B WatchdogSec= -- 2.45.0
