init: events are unblocked when the job fails
Bug #516713 reported by
Evan
This bug affects 3 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| upstart |
Triaged
|
Medium
|
Unassigned | ||
Bug Description
Given an oem-config job that starts on starting gdm and a failsafe-x job that starts on stopping oem-config, when oem-config exits nonzero, the gdm job will start before the failsafe-x job.
Revision history for this message
| Scott James Remnant (Canonical) (canonical-scott) wrote | #2 |
| summary: |
- events are unblocked when the event is failed + init: events are unblocked when the job fails |
| Changed in upstart: | |
| status: | New → Triaged |
| importance: | Undecided → Medium |
To post a comment you must log in.
This is bad because, for example:
# start apache
apache: failed to start
# start apache
At the point the second start command is run, the first might be still in post-stop. Even in the case of failure, the stop/start commands should still wait until the job settles again. Likewise events should remain blocked.