Former local file: bugs/018-always-mode-service-requiring-a-multi-service-fails-under-boot-s.md.

Status

Open as a config trap. No service in Hammerhead's current tree is affected.

0.4.0 rekeyed the requires carve-out from mode = always|single to [dependencies] protected = true and dropped the always exemption. On boot -s, multi services are STATE_INACTIVE (unsatisfied). An always service that requires a multi service then fails, where before the rekey it started anyway.

single-mode services still have the carve-out and are not exposed.

Direction

Config-load validation: refuse or warn at boot if always/single requires multi. Do not silently start the always service with an unmet requires.