You do not want systemd for your critical server need. Some problematic things remaining are: - pull an Ethernet cable and watch weird state enter via systemd

You do not want systemd for your critical server need. Some problematic things remaining are: - pull an Ethernet cable and watch weird state enter via systemd-networks - your long running custom-made daemon that spent many weeks building up cache goes down when Ethernet link state change It does not enable IP address to stay truly static IP when netlink device goes down. Nor does it leave the IP route table alone. Caveat emptor.