From 29def23f92bc38912c16d7ee2925035cf9f0ad60 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?J=C3=B6rg=20Thalheim?= Date: Mon, 13 Apr 2015 10:17:49 +0200 Subject: [PATCH] sshd socket activation --- ...ation-when-using-tmux-slash-screen.markdown | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) create mode 100644 source/_posts/2015-04-13-fix-sshd-socket-activation-when-using-tmux-slash-screen.markdown diff --git a/source/_posts/2015-04-13-fix-sshd-socket-activation-when-using-tmux-slash-screen.markdown b/source/_posts/2015-04-13-fix-sshd-socket-activation-when-using-tmux-slash-screen.markdown new file mode 100644 index 0000000..4e72b50 --- /dev/null +++ b/source/_posts/2015-04-13-fix-sshd-socket-activation-when-using-tmux-slash-screen.markdown @@ -0,0 +1,18 @@ +--- +layout: post +title: "Fix sshd socket activation when using tmux/screen" +date: 2015-04-13 10:04:18 +0200 +comments: true +categories: +--- + +When using sshd.socket to start sshd on demand, detaching from a tmux/screen +session will not work. The reason is once the ssh session is closed, systemd +will terminate all remaining processes in the sshd cgroups, which affects also +the tmux/screen background process. However this behaviour can be changed using +the following drop-in file: + +```plain /etc/systemd/system/sshd@.service.d/killmode.conf +[Service] +KillMode=process +```