On Sun, 21 Jun 2015 13:12:11 -0600 Kyle Amon <flesheno...@gmail.com>
wrote:
> Package: upstart
> Version: 1.11-5
> Severity: critical
> Justification: breaks unrelated software
>
> Dear Maintainer,
>
> Switching between sysvinit and systemd works. Switching from either
of them
> to upstart works. Switching from upstart to either of them fails.
This bug
> was well documented to the debian-users mailing list by "Thorsten
Holzman"
> <thorsten.holz...@gmx.de> on 11-21-14. There was one reply saying
to file a
> bug report, but he evidently did not. Please refer to his
description at the
> following URL...
https://lists.debian.org/debian-user/2014/11/msg01452.html.
>
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.
--
Cameron Norman
