startpar-bridge: does not notice, if upstart jobs are skipped
Bug #1338788 reported by
Dimitri John Ledkov
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| startpar (Ubuntu) |
Triaged
|
Undecided
|
Unassigned | ||
Bug Description
startpar-bridge: does not notice, if upstart jobs are skipped
For example, if init.d script is enabled, yet equivalent upstart job bails-out in pre-start.
| tags: | added: systemd-boot |
Revision history for this message
| Steve Langasek (vorlon) wrote | #1 |
| Changed in sysvinit (Ubuntu): | |
| assignee: | nobody → Dimitri John Ledkov (xnox) |
| status: | New → In Progress |
| status: | In Progress → Triaged |
Revision history for this message
| Martin Pitt (pitti) wrote | #2 |
| affects: | sysvinit (Ubuntu) → startpar (Ubuntu) |
| tags: | removed: systemd-boot |
| Changed in startpar (Ubuntu): | |
| assignee: | Dimitri John Ledkov (xnox) → nobody |
To post a comment you must log in.
If the upstart job has bailed out in pre-start, it has not started. The correct thing to do here is to notice the 'stopped' condition and have startpar treat that as a failed start - so that startpar does not wait for the job indefinitely, and also so that startpar does not start the dependent services.