Show warning on upgrade if there are /etc/init/*.override files

[Michael]

While upgrading from 14.04 to 16.04, I noticed that all of my previously disabled services got started again.

I disabled them by putting "manual" in e.g. /etc/init/isc-dhcp-server.conf - which is the "right" way I think. Luckily, there was no harm in my case, but this can put many people in risk by e.g. letting starting server services which are then accessible outside or even disrupt networks (like dhcp-servers). So in my oppinion the transition to systemd should honor "manual" flags in .override files - or at least warn if there are .override files.

[Martin Pitt (pitti)]

Sorry, we are not going to implement an upstart parser into systemd, and there is not even an 1-to-1 correspondence between upstart jobs and systemd units. So this can only ever be a heuristics, and "working in some cases" is worse (because not predictable) than "upstart overrides don't affect systemd units".

The "right way" to disable something in an init system agnostic way is "update-rc.d myservice disable". This will disable sysv init scripts, upstart jobs, and systemd units. But it's not realistic to expect that upstart and systemd can read each other's configuration files, sorry..

[Michael (3-ueuntu-4)]

Sorry, I think you missunterstood me ;-)

I meant NO reading upstart scripts from systemd, I meant a "big fat warning" during the system upgrade(!) if there are .override files - and perhaps a knob which disables services which were disabled in upstart. But the most important is the "big fat warning".

[Martin Pitt (pitti)]

OK. Packages don't have a good way of presenting such a warning, so this would need to go into the release upgrader.

[Michael (3-ueuntu-4)]

Any news on that one?