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
Desktop Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1542025
Title:
Transition from upstart to systemd should honor /etc/init/*.override
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1542025/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
