0.3: upstart utterly fails when /bin/sh symlink disappears
Bug #65024 reported by
Paul Sladen
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
upstart |
Fix Released
|
Low
|
Unassigned | ||
upstart (Ubuntu) |
Fix Released
|
Low
|
Unassigned |
Bug Description
upstart does not even allow a sulogin or reboot to work if '/bin/sh' is missing.
Ideally upstart should have a list of other known likely interactive shells on the system and at least give the user a chance to untangle their system.
Changed in upstart: | |
assignee: | nobody → keybuk |
importance: | Undecided → Low |
status: | Rejected → Confirmed |
Changed in upstart: | |
assignee: | keybuk → nobody |
assignee: | keybuk → nobody |
Changed in upstart: | |
status: | Confirmed → Triaged |
Changed in upstart: | |
status: | Fix Committed → Fix Released |
summary: |
- upstart utterly fails when /bin/sh symlink disappears + 0.3: upstart utterly fails when /bin/sh symlink disappears |
To post a comment you must log in.
The principal problem here is that /bin/sh is hardcoded as something to use in job_run_* -- we should check for exec failing and have some kind of fallback.
Perhaps just exec'ing /sbin/sulogin directly is appropriate?