** Changed in: upstart (Debian)
Status: New => Fix Released
--
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/1430479
Title:
"telinit u" under upstart (upstart's
** Bug watch added: Debian Bug tracker #789524
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=789524
** Also affects: upstart (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=789524
Importance: Unknown
Status: Unknown
--
You received this bug notification because
** Changed in: upstart (Debian)
Status: Unknown => New
--
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/1430479
Title:
"telinit u" under upstart (upstart's Restart
I've verified that the upgrade works now.
--
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/1430479
Title:
telinit u under upstart (upstart's Restart command) with systemd-
That's because perform_reexec() just reexec's argv[0], which used to be
/sbin/init. But that just changed pointing from upstart to pointing to
systemd. So upstart's function isn't actually conceptually wrong, but
perhaps we could run /sbin/upstart instead of argv[0] (which is likely
/sbin/init)?
So we either change upstart's perform_reexec() to run /sbin/upstart, or
we change systemd's telinit to not forward an u request to upstart,
and simply ignore the reload. The latter would break the intention of
glibc's restart though (but it's probably not a big deal).
--
You received this bug
Adam points out that we would need to fix that in trusty's and utopic's
upstart as well, so let's just work around that in systemd's telinit.
** Changed in: upstart (Ubuntu)
Importance: Critical = Medium
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
Fixing upstart to do the right thing is probably good anyway, but since
one can't go back in time and fix it, that won't solve the upgrade
issue. The only way to solve the upgrade issue is to make systemd not
forward the request, I imagine. It could potentially make the first
umount on reboot
http://anonscm.debian.org/cgit/pkg-
systemd/systemd.git/commit/?h=ubuntuid=0a5d8124369
** Changed in: systemd (Ubuntu)
Status: In Progress = Fix Committed
** Changed in: upstart (Ubuntu)
Status: New = Triaged
--
You received this bug notification because you are a member of
This bug was fixed in the package systemd - 219-4ubuntu5
---
systemd (219-4ubuntu5) vivid; urgency=medium
* Merge from experimental branch:
- /lib/lsb/init-functions.d/40-systemd: Don't ignore systemd unit
dependencies in degraded mode. (LP: #1429734)
-
As we have a workaround in systemd now, I untag this to clean up the bug
list.
** Tags removed: systemd-boot
--
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/1430479
Title:
11 matches
Mail list logo
