On 9 September 2014 14:38, Spence, Richard (EXT-Other - DE/Ulm) <[email protected]> wrote: > we have an additional requirement for which we can find no clean (direct) > solution in systemd: applications in the system should not stop for any > reason – any termination must be handled as a failure.
So... you want *all* terminations to be listed as "failed" in systemctl (!0), even when the exit status is "success" (0). At that point, you're just overloading the term "failure" to mean something it was never intended to mean. Therefore, any wrapper doing this is by definition a "[hack] that systemd is supposed to render unneccessary": systemd not helping you undermine reliable semantics natively is a *good* thing :-) Assuming you can't patch the service(s) in question to return correct error codes, just be explicit and use an appropriately named/commented wrapper to tell systemd (and anyone using the system) that you're doing something substandard. Regards, T G-R _______________________________________________ systemd-devel mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/systemd-devel
