d/xen-utils-common.xen.init: disable oom killer for xenstored
authorHans van Kranenburg <hans@knorrie.org>
Sun, 6 Sep 2020 20:54:15 +0000 (22:54 +0200)
committerHans van Kranenburg <hans@knorrie.org>
Thu, 19 Nov 2020 17:44:33 +0000 (18:44 +0100)
commita918994ee6505f6ee8b0157c0649b3f47b2cebb4
treeb86449571529643eb6843f824bffcf6c5dc580a6
parent04cb0acefdffd3c7cbde0c8e2ee81139ef505845
d/xen-utils-common.xen.init: disable oom killer for xenstored

In case of oom killer terminating some process, we'd rather not see
xenstored go. Xenstored has an in-memory database, and when starting the
process again, it would be empty, which is very inconvenient. Xenstored
should already score quite low and have a fairly low memory footprint,
but according to the user report, it happened.

Closes: #961511
Suggested-by: Samuel Thibault <sthibault@debian.org>
Signed-off-by: Hans van Kranenburg <hans@knorrie.org>
Acked-by: Ian Jackson <ijackson@chiark.greenend.org.uk>
debian/xen-utils-common.xen.init