Bug#824343: services don't start if legacy init script is a symlink to other filesystem

[Daniel Pocock]

Package: systemd
Version: 215-17+deb8u4
Severity: important

If the init script in /etc/init.d is a symlink to a script on another
filesystem such as /opt then systemd silently ignores it

It doesn't get started at boot

Using a command like

   systemctl start foo

gives no output, no error, but doesn't start it.

Using

   systemctl daemon-reload

finds it and starts it.

A workaround is to copy such scripts to /etc/init.d

Even if it can't be fixed to automatically use such scripts, maybe it
should show meaningful errors in this situation