Hi,
I'm having problems coping with a job that has multiple dependencies. Say
there's this service, ServiceA, that only needs to be running when both
ServiceB and ServiceC are running. Consequently, I want ServiceA to stop when
either ServiceB or ServiceC are stopped. This behavior is implemented through
the following conditions in ServiceA.conf:
---- snippet ----
start on (started ServiceB and started ServiceC)
stop on (stopped ServiceB or stopped ServiceC)
---- /snippet ----
The problem with this approach is that whenever ServiceA is stopped because
either ServiceB or ServiceC is stopped, ServiceA will not be started again if
the dependency service that stopped is started again (while I do need this
behavior). This because the started event for the dependency service that
didn't stop won't be emitted again.
Basically what would solve my problem, is the possibility to add job states
(besides events) to the start (/ stop) conditions.
Am I trying to use upstart for a job it isn't meant to do, or am I perhaps
doing something stupid and is there a better solution to this problem?
Any help is appreciated,
Thanks, Rein
_________________________________________________________________
Hotmail is redefining busy with tools for the New Busy. Get more from your
inbox.
http://www.windowslive.com/campaign/thenewbusy?ocid=PID28326::T:WLMTAGL:ON:WL:en-US:WM_HMP:042010_2--
upstart-devel mailing list
[email protected]
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/upstart-devel
