Systemd service life cycle

[Ralf Mardorf]

On Thu, 7 Apr 2016 16:05:36 +0200, Tom H wrote:
>> If a user edit units that cause unresolvable before/after conflicts,
>> how does systemd behave?  
>
>It's the same as anything else. If a user screws up the config of
>apache, iptables, nfs, nginx, postfix, smb, ssh, tomcat, etc, it's his
>or her problem.

To keep track of before/after requirements of many unit files, isn't
the same as staying on top of configuration files that aren't linked
by such a condition. It's already complicated to have both, "before"
and "after", instead of just "before" or "after", let alone the amount
of not self-explaining CameCase vocabulary, related to the before/after
syntax.