Thank you, Dan, that is great news.
--
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/1839290
Title:
systemd doesn't restart a service after crashes
Status in systemd:
Dan, is there any chance of this fix landing to xenial-proposed and
bionic-proposed?
Thanks.
--
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/1839290
Title:
systemd
For Bionic the problem also seems to fixed in
systemd=237-3ubuntu10.40~next20200212b1
foo and bar service files are exactly the same as in #8
Restart fails with systemd=237-3ubuntu10.38:
pono@systemd-bionic-test:~$ cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=18.04
Thank you, Dan.
The PPA build indeed fixes the test case in #8, for Xenial at the very least.
Sending SIGABRT to foo.service's process now causes services to restart, just
as intended. Here are the logs from the very same Xenial machine, as in #8:
$ sudo apt install
Here is a minimal example, courtesy of bl33pbl0p from the github issue.
I've double-checked it and it is valid test case for this issue:
$ systemctl cat foo
# /etc/systemd/system/foo.service
[Unit]
PartOf=bar.service
[Service]
ExecStart=/bin/sleep infinity
RestartSec=0s
Restart=always
$
Mathew, I've just checked the ubuntu-disco branch of systemd — it looks
like fix was backported in systemd=240-6ubuntu5 with a bunch of other
fixes, see debian/patches/Change-job-mode-of-manager-triggered-restarts-
to-JOB_REPL.patch. So disco was fixed before this bug was actually
filed.
Xenial
Hello, everyone.
Here's a debdiff patch with a backport of upstream patch to xenial
branch of systemd.
I've successfully built a modified source and deployed it to some xenial
machines — it works as intended, failed service restart correctly, just
as intended by Restart=always policy.
Before:
7 matches
Mail list logo
