Prevent Logoff from Killing tmux Session












1














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?






x11 tmux gnu-screen logout







share|improve this question



























    1














    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?






    x11 tmux gnu-screen logout







    share|improve this question

























      1












      1








      1







      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?






      x11 tmux gnu-screen logout







      share|improve this question













      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?






      x11 tmux gnu-screen logout




      x11 tmux gnu-screen logout






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked 1 hour ago









      palswim

      1,45111730




      1,45111730






















          1 Answer
          1






          active

          oldest

          votes


















          3














          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"





          share|improve this answer





















          • Additional discussion in a reddit thread.
            – palswim
            1 hour ago











          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
          });


          }
          });














          draft saved

          draft discarded


















          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









          3














          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"





          share|improve this answer





















          • Additional discussion in a reddit thread.
            – palswim
            1 hour ago
















          3














          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"





          share|improve this answer





















          • Additional discussion in a reddit thread.
            – palswim
            1 hour ago














          3












          3








          3






          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"





          share|improve this answer












          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"






          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered 1 hour ago









          palswim

          1,45111730




          1,45111730












          • Additional discussion in a reddit thread.
            – palswim
            1 hour ago


















          • Additional discussion in a reddit thread.
            – palswim
            1 hour ago
















          Additional discussion in a reddit thread.
          – palswim
          1 hour ago




          Additional discussion in a reddit thread.
          – palswim
          1 hour ago


















          draft saved

          draft discarded




















































          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.




          draft saved


          draft discarded














          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





















































          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







          -

          Popular posts from this blog

          A CLEAN and SIMPLE way to add appendices to Table of Contents and bookmarks

          Image
          0 I found a lot of questions abount appendices and ToC. Many users want appendices to be grouped in an Appendix part, however some problems arise with ToC, hyperref, PDF viewer bookmarks, and so on. There are different solutions which require extra packages, command patching and other extra code, however none of them satisfies me. I almost found an easy way to accomplish a good result, where appendices are added to bookmarks in the right way and hyperref links point to the right page. However, the number of the "Appendix" part page is wrong (it's the number of appendix A). Is there any EASY way to fix that? This is a MWE: documentclass{book} usepackage[nottoc,notlot,notlof]{tocbibind} usepackage{hyperref} begin{document} frontmatter tableofcontents mainmatter part{First} chapter{...
          Read more

          Calculate evaluation metrics using cross_val_predict sklearn

          Image
          1 In the sklearn.model_selection.cross_val_predict page it is stated: Generate cross-validated estimates for each input data point. It is not appropriate to pass these predictions into an evaluation metric. Can someone explain what does it mean? If this gives estimate of Y (y prediction) for every Y (true Y), why can't I calculate metrics such as RMSE or coefficient of determination using these results? python scikit-learn cross-validation share | improve this question edited Nov 28 '18 at 17:52 desertnaut 20.3k 7 43 79 ...
          Read more

          Insert data from modal to MySQL (multiple modal on website)

          Image
          0 I have problem with inserting data to MySQL from modal. My modal: <a href="#" class="badge badge-pill badge-success">6 komentarzy</a> <a href="#" class="badge badge-pill badge-danger">brak komentarzy</a> <a data-toggle="modal" href="#add_desk_comm_{$desk_['desk_id']}" data-target="#add_desk_comm_{$desk_['desk_id']}" class="ediiit">(dodaj)</a> <div class="modal fade" id="add_desk_comm_{$desk_['desk_id']}" tabindex="-1" role="dialog" aria-labelledby="edit_printer" aria-hidden="true"> <div class="modal-dialog" role="document"> ...
          Read more