conf/ups.conf.sample, docs/man/ups.conf.txt: further clarify behavior…

… of maxstartdelay [networkupstools#2134] Signed-off-by: Jim Klimov <jimklimov+nut@gmail.com>
jimklimov · Oct 28, 2023 · 6a08fae · 6a08fae
1 parent 672ecb3
commit 6a08fae
Show file tree

Hide file tree

Showing 2 changed files with 10 additions and 9 deletions.
diff --git a/conf/ups.conf.sample b/conf/ups.conf.sample
@@ -91,11 +91,11 @@ maxretry = 3
 #                Note that after this time upsdrvctl would just move
 #                along with its business (whether retrying the same
 #                driver if `maxretry>1`, or trying another driver if
-#                starting them all, or just exit); however the most
-#                recently started "stuck" driver process may be further
-#                initializing in the background, and might even succeed
-#                eventually.
-#                It would not be actively killed by upsdrvctl after
+#                starting them all, or just eventually exit); however,
+#                each such most recently started "stuck" driver process
+#                may be further initializing in the background, and
+#                might even succeed eventually.
+#                They would not be actively killed by upsdrvctl after
 #                this timeout expires.
 #
 #                The default is 45 seconds.

diff --git a/docs/man/ups.conf.txt b/docs/man/ups.conf.txt
@@ -249,10 +249,11 @@ system from getting stuck due to a broken driver or UPS.
 +
 Note that after this time `upsdrvctl` would just move along with its
 business (whether retrying the same driver if `maxretry>1`, or trying
-another driver if starting them all, or just exit); however the most
-recently started "stuck" driver process may be further initializing
-in the background, and might even succeed eventually. It would not be
-actively killed by `upsdrvctl` after this timeout expires.
+another driver if starting them all, or just eventually exit); however,
+each such most recently started "stuck" driver process may be further
+initializing in the background, and might even succeed eventually.
++
+They would not be actively killed by `upsdrvctl` after this timeout expires.
 +
 The default is 45 seconds.