[Bug 568860] Re: init: "before" functionality should block all services mentioned, not just the first
Cameron Norman
camerontnorman at gmail.com
Fri Nov 9 20:51:45 UTC 2018
It seems as though the issue is in job_class_induct_job()
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to upstart in Ubuntu.
https://bugs.launchpad.net/bugs/568860
Title:
init: "before" functionality should block all services mentioned, not
just the first
Status in upstart :
Triaged
Status in upstart package in Ubuntu:
Invalid
Bug description:
Binary package hint: upstart
There should be a way to express that a certain service has to be started before a list of other services. Currently we can do either:
a) start on (starting service1 or starting service2)
This will start our service before either service1 or service2, but
only one of them will be blocked until service has started. Or:
b) start on (starting service1 and starting service2)
Which will block service1 and service2 until out service starts, but
showstopper is that service won't be started unless both service1 and
service2 will start.
We need some mechanism to block a list of services from starting until
our service is ready, similar to the a) case from above, but where all
services mentioned in the dependency statement have to wait for the
service to start.
Inability to do this reliably and generically is stopping us from
ensuring that our service starts before any interactive login is
possible (console, graphics, network). I am also classifying this as a
security problem since for our customers it really is so.
To manage notifications about this bug go to:
https://bugs.launchpad.net/upstart/+bug/568860/+subscriptions
More information about the foundations-bugs
mailing list