Package Details: systemd-kill-fix 225-1

Git Clone URL: https://aur.archlinux.org/systemd-kill-fix.git (read-only)
Package Base: systemd-kill-fix
Description: system and service manager (with kill fix)
Upstream URL: http://www.freedesktop.org/wiki/Software/systemd
Licenses: GPL2, LGPL2.1
Conflicts: nss-myhostname, systemd, systemd-tools, udev
Provides: nss-myhostname, systemd=225, systemd-tools=225, udev=225
Replaces: nss-myhostname, systemd-tools, udev
Submitter: jamespharvey20
Maintainer: jamespharvey20
Last Packager: jamespharvey20
Votes: 2
Popularity: 0.000022
First Submitted: 2015-06-26 01:24
Last Updated: 2015-09-11 22:36

Required by (494)

Sources (6)

Latest Comments

jamespharvey20 commented on 2015-12-13 09:53

My apologies. Unexpected multiple severe family health issues. (All turned out well.)

Researching whether this package is now obsolete, or if not, how to update it. Looks like upstream commit e9db43d5 may wait for units to properly terminate under certain circumstances, which may eliminate the need to revert the commit to prevent data loss. Also looks like upstream commit a8c0f36 adds unified cgroup hierarchy support, on kernel 4.3+, which is currently in the testing repo, but not yet core. These changes (and maybe others) make upstream commit 743970d not simply revertable, due to conflicts.

At this time, if you want a newer systemd *and feel like being a little brave*, you can test core's systemd and see if the data loss issue is fixed as upstream says it is. Consensus upstream seems to be this issue is now resolved. See https://github.com/systemd/systemd/issues/317 - the original poster reports the issue seems to be fixed on Oct 29, and no one has said the issue remains.

sorpaas commented on 2015-09-07 09:23

systemd 225 is published.

jamespharvey20 commented on 2015-06-26 22:36

Identical to core's systemd 221-1, with two changes. First, reverts upstream commit 743970d which can cause data loss; reverting causes a chance of a 90 second timeout delay on reboot. Second, omits splash-arch.bmp because AUR currently limits the maximum filesize to 250k, and its 378k.

most common data loss from this is preventing bash from writing .bash_history. See https://github.com/systemd/systemd/pull/350#issuecomment-115327740 Appears upstream prefers to have chance of data loss, versus chance of 90 second timeout delay on shutdown.

Debian has reverted the same: http://anonscm.debian.org/cgit/pkg-systemd/systemd.git/commit/?id=00aaecd71

Ubunti has also: https://lists.ubuntu.com/archives/vivid-changes/2015-May/008558.html

Looks like RedHat may be doing so soon: https://bugzilla.redhat.com/show_bug.cgi?id=1170765 and https://bugzilla.redhat.com/show_bug.cgi?id=1141137

jamespharvey20 commented on 2015-06-26 22:36

Identical to core's systemd 221-1, with two changes. First, reverts upstream commit 743970d which can cause data loss; reverting causes a chance of a 90 second timeout delay on reboot. Second, omits splash-arch.bmp because AUR currently limits the maximum filesize to 250k, and its 378k.

most common data loss from this is preventing bash from writing .bash_history. See https://github.com/systemd/systemd/pull/350#issuecomment-115327740 Appears upstream prefers to have chance of data loss, versus chance of 90 second timeout delay on shutdown.

Debian has reverted the same: http://anonscm.debian.org/cgit/pkg-systemd/systemd.git/commit/?id=00aaecd71

Ubunti has also: https://lists.ubuntu.com/archives/vivid-changes/2015-May/008558.html

Looks like RedHat may be doing so soon: https://bugzilla.redhat.com/show_bug.cgi?id=1170765 and https://bugzilla.redhat.com/show_bug.cgi?id=1141137

jamespharvey20 commented on 2015-06-26 22:36

Identical to core's systemd 221-1, with two changes. First, reverts upstream commit 743970d which can cause data loss; reverting causes a chance of a 90 second timeout delay on reboot. Second, omits splash-arch.bmp because AUR currently limits the maximum filesize to 250k, and its 378k.

most common data loss from this is preventing bash from writing .bash_history. See https://github.com/systemd/systemd/pull/350#issuecomment-115327740 Appears upstream prefers to have chance of data loss, versus chance of 90 second timeout delay on shutdown.

Debian has reverted the same: http://anonscm.debian.org/cgit/pkg-systemd/systemd.git/commit/?id=00aaecd71

Ubunti has also: https://lists.ubuntu.com/archives/vivid-changes/2015-May/008558.html

Looks like RedHat may be doing so soon: https://bugzilla.redhat.com/show_bug.cgi?id=1170765 and https://bugzilla.redhat.com/show_bug.cgi?id=1141137