init: failing job blocking starting event means blocked job starts, even if failing job can recover and respawn
Bug #517198 reported by
Evan
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
upstart |
Triaged
|
Medium
|
Unassigned |
Bug Description
As requested.
I'm trying to have Ubuntu's failsafe-x job start when oem-config is stopping, before gdm starts. I would like the process of completing failsafe-x by starting $JOB (in this case oem-config) with XORGCONFIG=
It does not seem possible to express this in upstart at the moment.
summary: |
- unable to express oem-config/failsafe-x interaction + init: failing job blocking starting event means blocked job starts, even + if failing job can recover and respawn |
Changed in upstart: | |
status: | New → Triaged |
importance: | Undecided → Medium |
To post a comment you must log in.
Here is what I have at the moment, but it means that I'll have to start a display manager in oem-config- firstboot (run by oem-config), which involves some guessing for the correct one.