** Changed in: systemd (Fedora)
Status: Unknown => Invalid
** Changed in: systemd
Status: Unknown => Invalid
** Changed in: systemd (Fedora)
Importance: Unknown => Undecided
** Changed in: systemd
Importance: Unknown => Undecided
--
You received this bug notification
** Changed in: systemd (Debian)
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1448259
Title:
Systemd does not send SIGTERM first on shutdown
To manage
Tested with Ubuntu Mate 15.04 in Raspberry Pi 2 (test.c, included here).
It has systemd 219-7ubuntu5 package. After a reboot one can see that a
file testing.txt is created but its size is zero, i.e. it was not
given enough time to write the file contents. The fix is not working
with two laptops
This bug was fixed in the package systemd - 219-7ubuntu5
---
systemd (219-7ubuntu5) vivid; urgency=medium
* Revert upstream commit 743970d which immediately SIGKILLs units during
shutdown. This leads to problems like bash not being able to write its
history, mosh not saving
Olli, Maarten, could you please test the package in vivid-proposed
instead of my PPA, so that we can officially verify this to get it into
vivid-updates? Thank you in advance!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
For me the package in vivid-proposed works! :-)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1448259
Title:
Systemd does not send SIGTERM first on shutdown
To manage notifications about this bug
** Tags removed: verification-needed
** Tags added: verification-done
** Tags removed: systemd-bugs
** Tags added: systemd-boot
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1448259
Title:
Systemd
** Bug watch added: Debian Bug tracker #784720
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784720
** Also affects: systemd (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784720
Importance: Unknown
Status: Unknown
--
You received this bug notification because
** Changed in: systemd (Debian)
Status: Unknown = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1448259
Title:
Systemd does not send SIGTERM first on shutdown
To manage
This bug was fixed in the package systemd - 219-8ubuntu1
---
systemd (219-8ubuntu1) wily; urgency=medium
* Merge with Debian experimental branch. Remaining Ubuntu changes:
- Hack to support system-image read-only /etc, and modify files in
/etc/writable/ instead.
-
** Description changed:
It has been normal that applications first get the SIGTERM signal before
SIGKILL on shutdown/reboot in order to successfully finish any pending
tasks. Now it seem this logic has been changed to something else,
causing problems to mosh and many others:
Hello Olli, or anyone else affected,
Accepted systemd into vivid-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/systemd/219-7ubuntu5
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
This hasn't made it to -proposed or -updates yet, setting back to
Triaged.
** Changed in: systemd (Ubuntu Vivid)
Status: Fix Committed = Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Fixed in Debian experimental branch: http://anonscm.debian.org/cgit/pkg-
systemd/systemd.git/commit/?h=experimentalid=6068e872da
Cherry-picked into ubuntu branch: http://anonscm.debian.org/cgit/pkg-
systemd/systemd.git/commit/?h=ubuntuid=28640752854
** Changed in: systemd (Ubuntu Vivid)
It's still more or less the same, except that every unit and scope is
being shut down individually. man systemd.kill has the details.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1448259
Title:
I also tested tested the packages. The mosh case is now working but the
included test.c tester still fails this case.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1448259
Title:
Systemd does not
When I compare the documentation I see that with systemd SIGTERM has
been removed from it:
Old behavior: http://unixhelp.ed.ac.uk/CGI/man-cgi?shutdown+8
Systemd behavior: http://man7.org/linux/man-pages/man8/shutdown.8.html
Is it now that SIGTERM is sent in case-by-case basis to specific
** Changed in: systemd (Ubuntu Vivid)
Milestone: None = vivid-updates
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1448259
Title:
Systemd does not send SIGTERM first on shutdown
To manage
https://launchpad.net/~pitti/+archive/ubuntu/sru-test now has packages
with this fix. I can't upload it yet as there's a previous systemd being
tested in -proposed still. Feedback appreciated from all bug reporters,
though! (Also for bash history and mosh).
--
You received this bug notification
I tested the packages, and bash history is now properly retained during
a reboot :-)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1448259
Title:
Systemd does not send SIGTERM first on shutdown
To
** Also affects: systemd (Fedora) via
https://bugzilla.redhat.com/show_bug.cgi?id=1141137
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1448259
Title:
21 matches
Mail list logo
