From 7551c712d73f1d07f6dec2c9b8183a43204f4aa5 Mon Sep 17 00:00:00 2001 From: Laurent Bercot Date: Sat, 24 Jan 2026 16:17:39 +0000 Subject: Rename "sub" to "prescription" --- doc/s6-rc-set-fix.html | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) (limited to 'doc/s6-rc-set-fix.html') diff --git a/doc/s6-rc-set-fix.html b/doc/s6-rc-set-fix.html index eae3d69..564584f 100644 --- a/doc/s6-rc-set-fix.html +++ b/doc/s6-rc-set-fix.html @@ -33,7 +33,7 @@ dependency inconsistencies, and fixes them.
  • s6-rc-set-fix checks all the sets listed in sets... for dependency inconsistencies that may prevent s6-rc-set-commit from succeeding. If sets... is empty, all the sets in the repository are checked.
    • -
  • s6-rc-set-fix prints what it finds and changes the subs +
  • s6-rc-set-fix prints what it finds and changes the rxs of impacted services so the resulting set is consistent.
    • @@ -69,15 +69,15 @@ will be started at boot time than the set initially declared. This is the defaul
    -E, --no-force-essential
    If fixing a dependency inconsistency would imply moving a service down from the -always sub, or up to the always sub, when its service definition +always rx, or up to the always rx, when its service definition directory does not declare it as essential, do not attempt fixing it and fail the operation. This is the default. If such a situation occurs, it means that the set of services -provided in the stores is not consistent, and that +provided in the stores is not consistent, and that is what should be fixed.
    -e, --force-essential
    If fixing a dependency inconsistency would imply moving a service down from the -always sub, or up to the always sub, when its service definition +always rx, or up to the always rx, when its service definition directory does not declare it as essential, do it, even though it goes against a service definition in a store. This can help you keep a service set consistent until the store is fixed.
    -- cgit v1.3.1