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-change.html | 20 ++++++++++---------- 1 file changed, 10 insertions(+), 10 deletions(-) (limited to 'doc/s6-rc-set-change.html') diff --git a/doc/s6-rc-set-change.html b/doc/s6-rc-set-change.html index 3a718c4..8d0b13a 100644 --- a/doc/s6-rc-set-change.html +++ b/doc/s6-rc-set-change.html @@ -5,7 +5,7 @@ s6-rc: the s6-rc-set-change program - + @@ -20,18 +20,18 @@

s6-rc-set-change modifies a set by changing -the sub of some services. +the rx of some services.

Interface 

-     s6-rc-set-change [ -v verbosity ] [ -r repo ] [ -E | -e ] [ -f | -I fail|pull|warn ] [ -n ] set newsub services...
+     s6-rc-set-change [ -v verbosity ] [ -r repo ] [ -E | -e ] [ -f | -I fail|pull|warn ] [ -n ] set newrx services...
@@ -49,19 +49,19 @@ error messages will be written, and 2 or more adds informational messages.
-E, --no-force-essential
-
If a service needs to be moved to/from the always sub, fail and report +
If a service needs to be moved to/from the always rx, fail and report an error. This is the default. Services marked as always are normally defined in the stores with flag-essential, and inconsistencies between essential services should be resolved in the stores.
-e, --force-essential
-
Move services to/from the always sub if they need to be. This option +
Move services to/from the always rx if they need to be. This option should only be used temporarily until the store inconsistency is fixed. Be aware that moving a service from always to usable or masked may result in an unbootable set.
-f, --ignore-dependencies
-
Change services... to newsub, but do not change any other +
Change services... to newrx, but do not change any other services, even if the dependency graph would normally mandate it. This may result in an inconsistent set that you cannot commit.
@@ -69,7 +69,7 @@ in an inconsistent set that you cannot commit.
-I action, --if-dependencies-found=action
Determine what to do if a dependency would make the set inconsistent. For instance, if service A depends on service B, they are both -in the latent sub, and you are trying to change A to active +in the latent rx, and you are trying to change A to active without mentioning B, this would not work: in order to be brought up at boot time, A would first need B to also be brought up at boot time, so A can only be active if B also is. In that situation, @@ -78,7 +78,7 @@ what s6-rc-set-change does depends on the value of action:
  • fail: print an error message and exit 1.
  • warn: print a warning message and proceed. This is the default.
  • pull: print a warning message and pull the dependencies of -services... into newsub. (Or the reverse dependencies, if +services... into newrx. (Or the reverse dependencies, if you're trying to disable or mask services.
    • The warning messages are not printed if verbosity is 0.
    @@ -92,7 +92,7 @@ appropriate, but do not perform the actual modifications.
    0
    Success.
    1
    -I fail was given and dependencies prevented services... -from being changed to newsub.
    +from being changed to newrx.
    3
    A service in services... was not found in the reference database.
    4
    Invalid or corrupted reference database.
    100
    Incorrect usage.
    -- cgit v1.3.1