On Sun, Jun 28, 2015 at 11:26:00PM -0700, Cameron Norman wrote: > I fail to see how Upstart can do much to change this since Upstart's > reboot/telinit/shutdown/etc commands are not installed at the point where > you invoke reboot.
> The only way to do it from Upstart's side is to proxy requests from external > tools like systemctl or sysvinit's shutdown/telinit commands by: > * listening to /dev/initctl like systemd has a special daemon for > * taking systemd's name on the system bus so it can accept > shutdown/reboot/etc requests > The latter conflicts with systemd-shim's operation. It would be nigh > impossible to do without doing it in the shim itself... grr. upstart could certainly be adjusted to be compatible with the historical sysvinit rpc protocol (i.e., /dev/initctl). This has never been implemented in upstart because supporting switching away from upstart has never been a priority. But it is a bug in upstart that this is not supported, given that upstart is not the default in Debian. Whether this bug is severe enough to warrant the label "critical" and trigger removal from testing, I have no opinion. The package has already made it out the door in three stable releases with this issue; it doesn't obviously improve matters for users to not have the option of upgrading to a newer version of upstart, considering that's precisely the sort of situation that would cause the user to try to switch init systems and run into this bug at that point. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer http://www.debian.org/ slanga...@ubuntu.com vor...@debian.org
signature.asc
Description: Digital signature
