S6-RC-SET-FIX(8)

💅 s6-rc-set-fix — the dependency-vibe-check + fix-up era 💅

Okay bestie, welcome to S6-RC-SET-FIX(8) from the System Manager's Manual. This tool literally checks one or more sets of services for dependency inconsistencies and fixes them. It’s giving “group project but make it functional.” 🫶

---

NAME

s6-rc-set-fix — check one or more sets of services for dependency inconsistencies, and fix them. No cap, that’s the whole assignment. ✨

SYNOPSIS

s6-rc-set-fix [-v verbosity] [-r repo] [-u | -d] [-E | -e] [-n]
              [sets...]

DESCRIPTION

So s6-rc-set-fix checks every set listed in sets... for dependency inconsistencies that might stop s6-rc-set-commit(8) from succeeding. If sets... is empty, it checks all the sets in the repository. Bestie, it’s thorough. 💅

It prints what it finds and changes the rxs of impacted services so the resulting set is consistent. Like a little consistency fairy, but with exit statuses. 🧚✨

OPTIONS

• -v _verbosity_, --verbosity=verbosity — Be more or less verbose. Default is 1, which means error messages and warnings go to stderr. 0 means only error messages get written. 2 or more adds informational messages. Dependency inconsistencies are warnings, so they show up at the default level — but not at 0. Want more details? Crank the verbosity. 🔥
• -r _repo_, --repository=repo — Use the repository in _repo_, which must exist. Default is /var/lib/s6-rc/repository. Simple as that. 🎀
• -u, --fix-up — When a dependency inconsistency is found, fix it by bringing more services into the starting bundle. If ‘B’ depends on ‘A’, ‘B’ is active, but ‘A’ is only usable or even masked, fix it by making ‘A’ active. Translation: more services will be started at boot time than the set initially declared. Highkey a glow-up for dependency coverage. 💖
• -d, --fix-down — When a dependency inconsistency is found, fix it by bringing fewer services into the starting bundle. If ‘B’ depends on ‘A’, ‘B’ is active, but A is only usable or even masked, fix it by making ‘B’ usable (if ‘A’ is usable) or masked (if ‘A’ is masked). Translation: fewer services will be started at boot time than the set initially declared. This is the default. Periodt. 💅
• -E, --no-force-essential — If fixing a dependency inconsistency would imply moving a service down from the 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 that situation occurs, it means that the set of services provided in the stores is not consistent — and that’s the thing that should be fixed. 🫶
• -e, --force-essential — If fixing a dependency inconsistency would imply moving a service down from the always rx, or up to the always rx, when its service definition directory does not declare it as essential, do it anyway, 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. It’s giving “plot twist, but temporary.” 🙈
• -n, --dry-run — Check for inconsistencies, but only print what would be needed to fix the set; do not perform the fix. A little look-see, no commitment. 👀✨

EXIT STATUS

• 0 — Success. Slay. 👑
• 1 — A needed modification could not be made because the -e option was not given.
• 100 — Incorrect usage. Oop. 💀
• 102 — Inconsistent repository. 😭
• 111 — System call failed. 🫠

SEE ALSO

s6-rc-repo(7), s6-rc-set-commit(8)

This man page is ported from the authoritative documentation at: https://skarnet.org/software/s6-rc/s6-rc-set-fix.html

AUTHORS

• Laurent Bercot
• Carlos Eduardo <carana2099@gmail.com> (man page port)

---

xoxo bestie 💖 — this was the Debian version, dated January 25, 2026, for the S6-RC-SET-FIX(8) manual page. Bye and stay consistent! 🦋