[Bug 1273462] Re: Users can mistakenly run init.d scripts and cause problems if an equivalent upstart job already exists

[Steve Langasek]

> Thus in trusty you don't have the option to use dependency-based
> sysvinit scripts, you *have* to have rc?.d symlinks; and they are
> being used through upstart too via /etc/init/rc.conf.

In that case, any /etc/rc?.d symlink that shadows an upstart job is
still going to be doing the wrong thing at boot by trying to start a
service directly instead of via upstart.

I don't think anything here is going to be a "regression".  Only
"changes in undefined and racy behavior".  Yes, users may see some
surprising changes in boot-time behavior as a result of this change;
those will hopefully be changes for the better, but anything that relies
on the current behavior of running both the init script and the upstart
job at boot is deeply buggy and not supportable and should not block
this SRU.

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1273462

Title:
  Users can mistakenly run init.d scripts and cause problems if an
  equivalent upstart job already exists

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lsb/+bug/1273462/+subscriptions