Here is some good advice to handle systemd anxiety from adamo.
Configuration management / orchestration software already knows how to handle systemd and they do it well. Take advantage of that.
Unfortunately for me, there is a Chef server in our infra so old that doesn’t know how to handle systemd, and with the release of CentOS 7 (1511) it finally broke.
================================================================ Error executing action `restart` on resource 'service[iptables]' ================================================================ Chef::Exceptions::Service ------------------------- service[iptables]: unable to locate the init.d script!
It expects that all services have a script in /etc/init.d, so here is my quick hack around it.
$ ls -l /etc/init.d/iptables lrwxrwxrwx 1 root root 32 Dec 17 17:34 /etc/init.d/iptables -> /usr/local/bin/systemctl-wrapper $ cat /usr/local/bin/systemctl-wrapper #!/bin/bash # workaround for old school SysV persons # stsimb dec 2015 SERVICE="$(basename $0)" exec /bin/systemctl "$@" ${SERVICE}.service
Now we can spend more time migrating to our new Chef, that knows how to handle systemd.