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

          404 Error Contact Form 7 ajax form submitting

          Image
          0 The contact form does not work, and affects loading after one try. The chrome console shows the error message: POST http://example.com/wp-json/contact-form-7/v1/contact-forms/50/feedback 404 (Not Found) send @ jquery.js?ver=1.12.4:4 ajax @ jquery.js?ver=1.12.4:4 wpcf7.submit @ scripts.js?ver=5.0.3:346 (anonymous) @ scripts.js?ver=5.0.3:53 dispatch @ jquery.js?ver=1.12.4:3 r.handle @ jquery.js?ver=1.12.4:3 How to solve this issue? thanks in advance javascript wordpress contact-form-7 share | improve this question edited Jul 17 '18 at 5:39 Kiran Shahi 4,745 3 16 43 ...
          Read more

          How to know if a Active Directory user can login interactively

          Image
          1 I would like to know if and how is it possible to know if a AD user can login interactively (on a server) in a domain. I need to know if I can find it out using a LDAP search. Thanks. windows active-directory login user-permissions user-profile share | improve this question edited 1 hour ago yagmoth555 ♦ 11.6k 3 17 42 asked 1 hour ago Luigi Luigi 6 1 New contributor ...
          Read more

          Refactoring coordinates for Minecraft Pi buildings written in Python

          Image
          0 $begingroup$ I'm fairly new to coding and I wrote this script in Python for a house with a roof in Minecraft Pi. I've found different ways to write the coordinates to make the code base shorter, but I'm wondering if it is possible for me to refactor it any further so I don't have to list each coordinate line by line. import mcpi.minecraft as minecraft import mcpi.block as block mc = minecraft.Minecraft.create() p = mc.player.getTilePos() mc.setBlocks(p.x+1, p.y, p.z+1, #Main structure starting coordinates (DO NOT ALTER) p.x+19, p.y+4, p.z+6, #Structure size/coordinates (Alters cube size) block.STONE_BRICK) mc.setBlocks(p.x+2, p.y+1, p.z+2, #Hollowing out main structure interior p.x+18, p.y+3, p.z+5, block.AIR) mc.setBlocks(p.x, p.y...
          Read more