Am 15.01.2016 um 21:48 schrieb Michael Biebl: > Hi Alec > > Am 15.01.2016 um 21:42 schrieb Alec Leamas: >> It's more complicated. The systemd setup is three different services, >> the sysV one. There is no systemd service directly corresponding to >> the sysV one. In other words, here is two things taking place at once: >> a major upgrade + sysV -> systemd. > > In that case, I would probably mask the sysv init script under systemd, > i.e ship a symlink /lib/systemd/systemd/sysvinitname → /dev/null > > This way, it is prevented, that the sysv init script is run (by > accident) under systemd. An example for that is alsa-utils: The sysv init script is named /etc/init.d/alsa-utils The systemd service units: /lib/systemd/system/alsa-store.service /lib/systemd/system/alsa-state.service /lib/systemd/system/alsa-restore.service And /lib/systemd/system/alsa-utils.service is a symlink pointing at /dev/null. Another approach, as e.g. used by openvpn, where /etc/init.d/openvpn corresponds to a multitude of systemd service units, is to to use a dummy service or target, which represents the old sysv name. Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?
Description: OpenPGP digital signature