Prevent Logoff from Killing tmux Session
Clash Royale CLAN TAG#URR8PPP
I have noticed that a logoff (log out) from my X user session will kill any tmux session I have initiated, even sessions I had run with sudo tmux and similar commands. I am sure that this formerly did not happen, but some recent change has effected this behavior.
How do I maintain these tmux (or screen) sessions, even after I end my X session?
systemd tmux gnu-screen session logout
edited Dec 21 '18 at 11:30
Gilles
529k12810601585
asked Dec 21 '18 at 6:19
palswim
1,59611732
add a comment |
I have noticed that a logoff (log out) from my X user session will kill any tmux session I have initiated, even sessions I had run with sudo tmux and similar commands. I am sure that this formerly did not happen, but some recent change has effected this behavior.
How do I maintain these tmux (or screen) sessions, even after I end my X session?
systemd tmux gnu-screen session logout
edited Dec 21 '18 at 11:30
Gilles
529k12810601585
asked Dec 21 '18 at 6:19
palswim
1,59611732
if you are interested, unix.stackexchange.com/questions/490243/…
– Tim
Dec 22 '18 at 4:29
What is "X user session" that you "logoff from"? Its process name is ...?
– Tim
Dec 22 '18 at 4:33
add a comment |
I have noticed that a logoff (log out) from my X user session will kill any tmux session I have initiated, even sessions I had run with sudo tmux and similar commands. I am sure that this formerly did not happen, but some recent change has effected this behavior.
How do I maintain these tmux (or screen) sessions, even after I end my X session?
systemd tmux gnu-screen session logout
edited Dec 21 '18 at 11:30
Gilles
529k12810601585
asked Dec 21 '18 at 6:19
palswim
1,59611732
I have noticed that a logoff (log out) from my X user session will kill any tmux session I have initiated, even sessions I had run with sudo tmux and similar commands. I am sure that this formerly did not happen, but some recent change has effected this behavior.
How do I maintain these tmux (or screen) sessions, even after I end my X session?
systemd tmux gnu-screen session logout
systemd tmux gnu-screen session logout
edited Dec 21 '18 at 11:30
Gilles
529k12810601585
asked Dec 21 '18 at 6:19
palswim
1,59611732
edited Dec 21 '18 at 11:30
Gilles
529k12810601585
asked Dec 21 '18 at 6:19
palswim
1,59611732
edited Dec 21 '18 at 11:30
Gilles
529k12810601585
edited Dec 21 '18 at 11:30
Gilles
529k12810601585
edited Dec 21 '18 at 11:30
Gilles
529k12810601585
529k12810601585
asked Dec 21 '18 at 6:19
palswim
1,59611732
asked Dec 21 '18 at 6:19
palswim
1,59611732
asked Dec 21 '18 at 6:19
palswim
1,59611732
1,59611732
if you are interested, unix.stackexchange.com/questions/490243/…
– Tim
Dec 22 '18 at 4:29
What is "X user session" that you "logoff from"? Its process name is ...?
– Tim
Dec 22 '18 at 4:33
add a comment |
if you are interested, unix.stackexchange.com/questions/490243/…
– Tim
Dec 22 '18 at 4:29
What is "X user session" that you "logoff from"? Its process name is ...?
– Tim
Dec 22 '18 at 4:33
if you are interested, unix.stackexchange.com/questions/490243/…
– Tim
Dec 22 '18 at 4:29
if you are interested, unix.stackexchange.com/questions/490243/…
– Tim
Dec 22 '18 at 4:29
What is "X user session" that you "logoff from"? Its process name is ...?
– Tim
Dec 22 '18 at 4:33
What is "X user session" that you "logoff from"? Its process name is ...?
– Tim
Dec 22 '18 at 4:33
add a comment |
1 Answer
1
active
oldest
votes
This "feature" has existed in systemd previously, but the systemd developers decided to effect a change in the default, to enable the setting for termination of child processes upon log out of a session.
You can revert this setting in your logind.conf (/etc/systemd/logind.conf):
KillUserProcesses=no
You can also run tmux with a systemd-run wrapper like the following:
systemd-run --scope --user tmux
For these systems, you may just want to alias the tmux (or screen) command:
alias tmux="systemd-run --scope --user tmux"
answered Dec 21 '18 at 6:19
palswim
1,59611732
Additional discussion in a reddit thread.
– palswim
Dec 21 '18 at 6:20
3
… and in many other places. In the Debian bug that that refers to, I explained how one could actually makesystemd-loginddo the right thing. bugs.debian.org/cgi-bin/bugreport.cgi?bug=825394#221
– JdeBP
Dec 21 '18 at 9:23
@JdeBP Thanks for telling us that sending SIGHUP instead of SIGTERM and SIGKILL allows daemons to survive closing of a systemd logind session. I'd also appreciate if you could also consider unix.stackexchange.com/questions/484344/… and unix.stackexchange.com/a/490435/674
– Tim
Dec 22 '18 at 5:14
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "106"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f490267%2fprevent-logoff-from-killing-tmux-session%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
This "feature" has existed in systemd previously, but the systemd developers decided to effect a change in the default, to enable the setting for termination of child processes upon log out of a session.
You can revert this setting in your logind.conf (/etc/systemd/logind.conf):
KillUserProcesses=no
You can also run tmux with a systemd-run wrapper like the following:
systemd-run --scope --user tmux
For these systems, you may just want to alias the tmux (or screen) command:
alias tmux="systemd-run --scope --user tmux"
answered Dec 21 '18 at 6:19
palswim
1,59611732
Additional discussion in a reddit thread.
– palswim
Dec 21 '18 at 6:20
3
… and in many other places. In the Debian bug that that refers to, I explained how one could actually makesystemd-loginddo the right thing. bugs.debian.org/cgi-bin/bugreport.cgi?bug=825394#221
– JdeBP
Dec 21 '18 at 9:23
@JdeBP Thanks for telling us that sending SIGHUP instead of SIGTERM and SIGKILL allows daemons to survive closing of a systemd logind session. I'd also appreciate if you could also consider unix.stackexchange.com/questions/484344/… and unix.stackexchange.com/a/490435/674
– Tim
Dec 22 '18 at 5:14
add a comment |
This "feature" has existed in systemd previously, but the systemd developers decided to effect a change in the default, to enable the setting for termination of child processes upon log out of a session.
You can revert this setting in your logind.conf (/etc/systemd/logind.conf):
KillUserProcesses=no
You can also run tmux with a systemd-run wrapper like the following:
systemd-run --scope --user tmux
For these systems, you may just want to alias the tmux (or screen) command:
alias tmux="systemd-run --scope --user tmux"
answered Dec 21 '18 at 6:19
palswim
1,59611732
Additional discussion in a reddit thread.
– palswim
Dec 21 '18 at 6:20
3
… and in many other places. In the Debian bug that that refers to, I explained how one could actually makesystemd-loginddo the right thing. bugs.debian.org/cgi-bin/bugreport.cgi?bug=825394#221
– JdeBP
Dec 21 '18 at 9:23
@JdeBP Thanks for telling us that sending SIGHUP instead of SIGTERM and SIGKILL allows daemons to survive closing of a systemd logind session. I'd also appreciate if you could also consider unix.stackexchange.com/questions/484344/… and unix.stackexchange.com/a/490435/674
– Tim
Dec 22 '18 at 5:14
add a comment |
This "feature" has existed in systemd previously, but the systemd developers decided to effect a change in the default, to enable the setting for termination of child processes upon log out of a session.
You can revert this setting in your logind.conf (/etc/systemd/logind.conf):
KillUserProcesses=no
You can also run tmux with a systemd-run wrapper like the following:
systemd-run --scope --user tmux
For these systems, you may just want to alias the tmux (or screen) command:
alias tmux="systemd-run --scope --user tmux"
answered Dec 21 '18 at 6:19
palswim
1,59611732
This "feature" has existed in systemd previously, but the systemd developers decided to effect a change in the default, to enable the setting for termination of child processes upon log out of a session.
You can revert this setting in your logind.conf (/etc/systemd/logind.conf):
KillUserProcesses=no
You can also run tmux with a systemd-run wrapper like the following:
systemd-run --scope --user tmux
For these systems, you may just want to alias the tmux (or screen) command:
alias tmux="systemd-run --scope --user tmux"
answered Dec 21 '18 at 6:19
palswim
1,59611732
answered Dec 21 '18 at 6:19
palswim
1,59611732
answered Dec 21 '18 at 6:19
palswim
1,59611732
answered Dec 21 '18 at 6:19
palswim
1,59611732
1,59611732
Additional discussion in a reddit thread.
– palswim
Dec 21 '18 at 6:20
3
… and in many other places. In the Debian bug that that refers to, I explained how one could actually makesystemd-loginddo the right thing. bugs.debian.org/cgi-bin/bugreport.cgi?bug=825394#221
– JdeBP
Dec 21 '18 at 9:23
@JdeBP Thanks for telling us that sending SIGHUP instead of SIGTERM and SIGKILL allows daemons to survive closing of a systemd logind session. I'd also appreciate if you could also consider unix.stackexchange.com/questions/484344/… and unix.stackexchange.com/a/490435/674
– Tim
Dec 22 '18 at 5:14
add a comment |
Additional discussion in a reddit thread.
– palswim
Dec 21 '18 at 6:20
3
… and in many other places. In the Debian bug that that refers to, I explained how one could actually makesystemd-loginddo the right thing. bugs.debian.org/cgi-bin/bugreport.cgi?bug=825394#221
– JdeBP
Dec 21 '18 at 9:23
@JdeBP Thanks for telling us that sending SIGHUP instead of SIGTERM and SIGKILL allows daemons to survive closing of a systemd logind session. I'd also appreciate if you could also consider unix.stackexchange.com/questions/484344/… and unix.stackexchange.com/a/490435/674
– Tim
Dec 22 '18 at 5:14
Additional discussion in a reddit thread.
– palswim
Dec 21 '18 at 6:20
Additional discussion in a reddit thread.
– palswim
Dec 21 '18 at 6:20
3
3
… and in many other places. In the Debian bug that that refers to, I explained how one could actually make
systemd-logind do the right thing. bugs.debian.org/cgi-bin/bugreport.cgi?bug=825394#221– JdeBP
Dec 21 '18 at 9:23
… and in many other places. In the Debian bug that that refers to, I explained how one could actually make
systemd-logind do the right thing. bugs.debian.org/cgi-bin/bugreport.cgi?bug=825394#221– JdeBP
Dec 21 '18 at 9:23
@JdeBP Thanks for telling us that sending SIGHUP instead of SIGTERM and SIGKILL allows daemons to survive closing of a systemd logind session. I'd also appreciate if you could also consider unix.stackexchange.com/questions/484344/… and unix.stackexchange.com/a/490435/674
– Tim
Dec 22 '18 at 5:14
@JdeBP Thanks for telling us that sending SIGHUP instead of SIGTERM and SIGKILL allows daemons to survive closing of a systemd logind session. I'd also appreciate if you could also consider unix.stackexchange.com/questions/484344/… and unix.stackexchange.com/a/490435/674
– Tim
Dec 22 '18 at 5:14
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f490267%2fprevent-logoff-from-killing-tmux-session%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
if you are interested, unix.stackexchange.com/questions/490243/…
– Tim
Dec 22 '18 at 4:29
What is "X user session" that you "logoff from"? Its process name is ...?
– Tim
Dec 22 '18 at 4:33