init: failing job blocking starting event means blocked job starts, even if failing job can recover and respawn

Reported by Evan Dandrea on 2010-02-04
8
This bug affects 2 people
Affects Status Importance Assigned to Milestone
upstart
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=/etc/X11/xorg.conf.failsafe (/etc/gdm/failsafeXinit) to jump back to gdm starting with oem-config starting just before it (so that successful completion of oem-config starts gdm/kdm), and somehow still ensure that oem-config gets started with XORGCONFIG=/etc/X11/xorg.conf.failsafe.

It does not seem possible to express this in upstart at the moment.

Evan Dandrea (ev) wrote :

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.

Evan Dandrea (ev) wrote :
Evan Dandrea (ev) wrote :
Evan Dandrea (ev) wrote :

For what it's worth, I've modified /usr/sbin/oem-config-prepare to exit nonzero when X is unable to start in this case.

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.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers