On Wednesday 10 August 2016, Andrei Borzenkov wrote:
On Wed, Aug 10, 2016 at 11:42 AM, Ruediger Meier <sweet_f_a@gmx.de> wrote:
$ systemctl status 2944 session-56.scope - Session 56 of user rudi Loaded: loaded (/run/systemd/system/session-56.scope; static) Drop-In: /run/systemd/system/session-56.scope.d └─90-After-systemd-logind\x2eservice.conf, 90-After-systemd-user-sessions\x2eservice.conf, 90-Description.conf, 90-KillMode.conf, 90-SendSIGHUP.conf, 90-Slice.conf Active: active (abandoned) since Wed 2016-08-10 10:28:11 CEST; 5min ago CGroup: /user.slice/user-1000.slice/session-56.scope ├─2943 ./sigtest2 └─2944 ./sigtest1
$ cat /run/systemd/system/session-56.scope.d/90-SendSIGHUP.conf [Scope] SendSIGHUP=yes
So, where does the "90-SendSIGHUP.conf" comes from?
From logind creating session scope.
src/login/logind-dbus.c:manager_start_scope()
/* Make sure that the session shells are terminated with * SIGHUP since bash and friends tend to ignore SIGTERM */ r = sd_bus_message_append(m, "(sv)", "SendSIGHUP", "b", true); if (r < 0) return r;
This makes no sense to me, processes which want to ignore SIGTERM get what they deserve later: SIGKILL (after a ridiculous long timeout, default 90s). BTW other processes may reload their configs on SIGHUP ... while shutdown. Moreover why it sends SIGHUP two times plus SIGTERM one time? Just to check if any program has a rock-solid signal handler implemented?
As far as I can tell it is not configurable. You may consider using systemd-run to start those processes outside of normal session scope.
This means I have to start basically _any_ process with systemd-run? Should I try to set my login shells to "systemd-run --user /bin/bash" BTW in future systemd-logind seems to be even more agressive: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=825394 Hope that openSUSE does not use this insane default. cu, Rudi -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org