touch-packages team mailing list archive
-
touch-packages team
-
Mailing list archive
-
Message #18299
[Bug 1370329] [NEW] systemd's reboot/shutdown programs don't work under upstart
Public bug reported:
Installing systemd-sysv replaces upstart's "reboot", "poweroff" and
friends. systemd's binaries currently don't know how to talk to upstart
to "forward" the request to upstart. This breaks a transition to systemd
as default init which doesn't just change the boot= kernel parameter but
installs systemd-sysv.
The same problem happens when systemd-sysv is installed but the system
gets booted with init=/sbin/upstart.
It would be useful if one could do "initctl reboot", so that there's
always a way to reboot the system when using a different init= than
/sbin/init.
** Affects: systemd (Ubuntu)
Importance: Medium
Status: Triaged
** Tags: systemd-boot
** Changed in: systemd (Ubuntu)
Status: New => Triaged
** Changed in: systemd (Ubuntu)
Importance: Undecided => Medium
** Tags added: systemd-boot
** Description changed:
Installing systemd-sysv replaces upstart's "reboot", "poweroff" and
friends. systemd's binaries currently don't know how to talk to upstart
to "forward" the request to upstart. This breaks a transition to systemd
as default init which doesn't just change the boot= kernel parameter but
installs systemd-sysv.
+ The same problem happens when systemd-sysv is installed but the system
+ gets booted with init=/sbin/upstart.
+
It would be useful if one could do "initctl reboot", so that there's
always a way to reboot the system when using a different init= than
/sbin/init.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1370329
Title:
systemd's reboot/shutdown programs don't work under upstart
Status in “systemd” package in Ubuntu:
Triaged
Bug description:
Installing systemd-sysv replaces upstart's "reboot", "poweroff" and
friends. systemd's binaries currently don't know how to talk to
upstart to "forward" the request to upstart. This breaks a transition
to systemd as default init which doesn't just change the boot= kernel
parameter but installs systemd-sysv.
The same problem happens when systemd-sysv is installed but the system
gets booted with init=/sbin/upstart.
It would be useful if one could do "initctl reboot", so that there's
always a way to reboot the system when using a different init= than
/sbin/init.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1370329/+subscriptions
Follow ups
References