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..
** Changed in: systemd (Ubuntu)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1542025
Title:
Transition from upstart to systemd should honor /etc/init/*.override
Status in systemd package in Ubuntu:
Won't Fix
Bug description:
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.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1542025/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
