True, but systemd units work much better, especially if you need to run
multiple dsmcad instance for some reason. Systemd knows the PIDs of
every service without trying to guess using pidof klusges so service
restarts won't kill wrong processes. I don't know why TSM clients still
ship with only the old school systemV init scripts, but at least in
linux you got something, unlike on unix platforms. Basic systemd service
unit is easy to do: consult the systemd.service(5) and systemd.exec(5)
manual pages.

There are some interesting possibilities, like perhaps using
ReadWriteDirectories, ReadOnlyDirectories, Capabilities to try somewhat
mitigate security risks involved in running the dsmcad (which ALWAYS
listens to the network!) as root.

On Sun, 2016-04-24 at 16:24 +0200, Florian Bachmann wrote:
> I believe systemd will automatically fall back to using Sys V init scripts
> if no .service file is available.
>
> E.g. systemctl enable|disable servicename will execute the corresponding
> chkconfig command and systemctl start|stop|restart servicename will invoke
> the Sys V init script with the appropriate parameter.