Can not switch back to sysvinit
Bug #291613 reported by
Loïc Minier
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| upstart |
Won't Fix
|
Undecided
|
Unassigned | ||
| sysvinit (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Bug Description
Hi,
When reinstalling sysvinit on a system running upstart, telinit can not talk to the currently running init. For the same reason, it's not possible to ask for a reboot.
This is less an use case than moving from sysvinit to upstart -- which does work fine -- but I thought it should be reported.
Bye
Revision history for this message
| Loïc Minier (lool) wrote | #1 |
Revision history for this message
| Scott James Remnant (Canonical) (canonical-scott) wrote | #2 |
| Changed in upstart: | |
| status: | New → Won't Fix |
Revision history for this message
| Loïc Minier (lool) wrote | #3 |
Revision history for this message
| Scott James Remnant (Canonical) (canonical-scott) wrote | #4 |
Revision history for this message
| Luke J Militello (kilahurtz) wrote | #5 |
To post a comment you must log in.
(Not terribly useful on an Ubuntu system, but it's easier for me to setup an Ubuntu vm right now) the exact output is:
on install:
...
Setting up sysvinit (2.86.ds1-
init: timeout opening/writing control channel /dev/initctl
on reboot:
Broadcast message from root blahblah
The system is going down for reboot NOW!
shutdown: timeout opening/writing control channel /dev/initctl
init: timeout opening/writing control channel /dev/initctl