It appears you received a response here: <a href="https:&#x2F;&#x2F;www.reddit.com&#x2F;r&#x2F;linux&#x2F;comments&#x2F;3od733&#x2F;structural_and_semantic_deficiencies_in_the&#x2F;cvwf201" rel="nofollow">https:&#x2F;&#x2F;www.reddit.com&#x2F;r&#x2F;linux&#x2F;comments&#x2F;3od733&#x2F;structural_an...</a><p>You do indeed misunderstand the point about execution composition. Chain loading is indeed configuration-related, not service-related. It&#x27;s a much more flexible and visible method than internal structures. Delegated restarters then can be deterministic as they reuse process management.<p>C&#x2F;R solutions don&#x27;t require special integration, that&#x27;s the point. They work on unmodified processes, unlike readiness notification. This is I think a reasonable trade-off for the potential decrease in reliability, as the feature comes with a double advantage of startup optimization and then readiness notification is generally not <i>that</i> critical, in light of regular Unix process semantics. C&#x2F;R is also constantly improving and reasonably stable for base use cases these days.