init: cancelling pre-stop using "start" will cause ignoring of exited process during pre-stop invocation
Bug #539175 reported by
Scott James Remnant (Canonical)
This bug affects 3 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| upstart |
Triaged
|
Medium
|
Unassigned | ||
Bug Description
If a job has a pre-stop script, and calls "start" from within that to change the goal back to start ... and while that script was running, the process actually died ... the start invocation will cancel the stop of the job - even due to the process death.
The job will remain running, with no main process pid recorded
Revision history for this message
| Scott James Remnant (Canonical) (canonical-scott) wrote | #1 |
| Changed in upstart: | |
| status: | New → Triaged |
| importance: | Undecided → Medium |
To post a comment you must log in.
We're really going to have to think of start and stop commands, and events, as queued transactions on a job - it's ok to cancel one, but not the other!