From: Hans van Kranenburg Date: Sun, 6 Sep 2020 20:54:15 +0000 (+0200) Subject: d/xen-utils-common.xen.init: disable oom killer for xenstored X-Git-Tag: archive/raspbian/4.14.0+80-gd101b417b7-1+rpi1^2~35 X-Git-Url: https://dgit.raspbian.org/?a=commitdiff_plain;h=a918994ee6505f6ee8b0157c0649b3f47b2cebb4;p=xen.git 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 Signed-off-by: Hans van Kranenburg Acked-by: Ian Jackson --- diff --git a/debian/xen-utils-common.xen.init b/debian/xen-utils-common.xen.init index a38fd00c01..1a64d6767e 100644 --- a/debian/xen-utils-common.xen.init +++ b/debian/xen-utils-common.xen.init @@ -226,7 +226,8 @@ xenstored_start() eval "try_xenstored=\$$try_xenstored_var" if [ -x $try_xenstored ]; then if start-stop-daemon --start --quiet \ - --pidfile "$XENSTORED_PIDFILE" --exec "$try_xenstored" -- \ + --pidfile "$XENSTORED_PIDFILE" \ + --exec /usr/bin/choom -- -n -1000 "$try_xenstored" -- \ $XENSTORED_ARGS --pid-file "$XENSTORED_PIDFILE"; then started_xenstored=$try_xenstored break