How can I leave the tmux server running after the last session exists?

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP












0














I'm trying to run tmux as a systemd user service ~/.config/systemd/user/tmux.service. When I start the service with systemd --user start tmux and then run tmux from a terminal, it seems to correctly connect to the tmux server of the service.



However, when I close the last session, the tmux service stops. This is a problem because I want the tmux server to stay available for SSH clients. How do I prevent the tmux server from automatically stopping after the last session is closed?



[Service]
Type=forking
ExecStart=tmux new-session -s %u -d
ExecStop=tmux kill-session -t %u

[Install]
WantedBy=default.target


Solution:



[Service]
Type=forking
ExecStart=tmux new -s dummy -d
ExecStop=-tmux kill-server
Restart=on-success

[Install]
WantedBy=default.target









share|improve this question




























    0














    I'm trying to run tmux as a systemd user service ~/.config/systemd/user/tmux.service. When I start the service with systemd --user start tmux and then run tmux from a terminal, it seems to correctly connect to the tmux server of the service.



    However, when I close the last session, the tmux service stops. This is a problem because I want the tmux server to stay available for SSH clients. How do I prevent the tmux server from automatically stopping after the last session is closed?



    [Service]
    Type=forking
    ExecStart=tmux new-session -s %u -d
    ExecStop=tmux kill-session -t %u

    [Install]
    WantedBy=default.target


    Solution:



    [Service]
    Type=forking
    ExecStart=tmux new -s dummy -d
    ExecStop=-tmux kill-server
    Restart=on-success

    [Install]
    WantedBy=default.target









    share|improve this question


























      0












      0








      0







      I'm trying to run tmux as a systemd user service ~/.config/systemd/user/tmux.service. When I start the service with systemd --user start tmux and then run tmux from a terminal, it seems to correctly connect to the tmux server of the service.



      However, when I close the last session, the tmux service stops. This is a problem because I want the tmux server to stay available for SSH clients. How do I prevent the tmux server from automatically stopping after the last session is closed?



      [Service]
      Type=forking
      ExecStart=tmux new-session -s %u -d
      ExecStop=tmux kill-session -t %u

      [Install]
      WantedBy=default.target


      Solution:



      [Service]
      Type=forking
      ExecStart=tmux new -s dummy -d
      ExecStop=-tmux kill-server
      Restart=on-success

      [Install]
      WantedBy=default.target









      share|improve this question















      I'm trying to run tmux as a systemd user service ~/.config/systemd/user/tmux.service. When I start the service with systemd --user start tmux and then run tmux from a terminal, it seems to correctly connect to the tmux server of the service.



      However, when I close the last session, the tmux service stops. This is a problem because I want the tmux server to stay available for SSH clients. How do I prevent the tmux server from automatically stopping after the last session is closed?



      [Service]
      Type=forking
      ExecStart=tmux new-session -s %u -d
      ExecStop=tmux kill-session -t %u

      [Install]
      WantedBy=default.target


      Solution:



      [Service]
      Type=forking
      ExecStart=tmux new -s dummy -d
      ExecStop=-tmux kill-server
      Restart=on-success

      [Install]
      WantedBy=default.target






      tmux






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Dec 16 at 18:47

























      asked Dec 14 at 19:19









      danijar

      3911313




      3911313




















          1 Answer
          1






          active

          oldest

          votes


















          2














          tmux has an option exit-unattached which says If enabled, the server will exit when there are no attached clients, which you can disable with



          set-option -s exit-unattached off


          in your ~/.tmux.conf, but this doesn't seem to have any effect for me (on
          or off), or I have misunderstood what it means.



          You can ask systemd to restart your service on exit by adding the line



          Restart=on-success


          You also need to edit the ExecStop to prefix the command with - in order to ignore the failure of the kill-session command when restarting (because the server is no longer running by then).



          ExecStop=-/usr/bin/tmux kill-session -t %u





          share|improve this answer




















            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%2f488043%2fhow-can-i-leave-the-tmux-server-running-after-the-last-session-exists%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









            2














            tmux has an option exit-unattached which says If enabled, the server will exit when there are no attached clients, which you can disable with



            set-option -s exit-unattached off


            in your ~/.tmux.conf, but this doesn't seem to have any effect for me (on
            or off), or I have misunderstood what it means.



            You can ask systemd to restart your service on exit by adding the line



            Restart=on-success


            You also need to edit the ExecStop to prefix the command with - in order to ignore the failure of the kill-session command when restarting (because the server is no longer running by then).



            ExecStop=-/usr/bin/tmux kill-session -t %u





            share|improve this answer

























              2














              tmux has an option exit-unattached which says If enabled, the server will exit when there are no attached clients, which you can disable with



              set-option -s exit-unattached off


              in your ~/.tmux.conf, but this doesn't seem to have any effect for me (on
              or off), or I have misunderstood what it means.



              You can ask systemd to restart your service on exit by adding the line



              Restart=on-success


              You also need to edit the ExecStop to prefix the command with - in order to ignore the failure of the kill-session command when restarting (because the server is no longer running by then).



              ExecStop=-/usr/bin/tmux kill-session -t %u





              share|improve this answer























                2












                2








                2






                tmux has an option exit-unattached which says If enabled, the server will exit when there are no attached clients, which you can disable with



                set-option -s exit-unattached off


                in your ~/.tmux.conf, but this doesn't seem to have any effect for me (on
                or off), or I have misunderstood what it means.



                You can ask systemd to restart your service on exit by adding the line



                Restart=on-success


                You also need to edit the ExecStop to prefix the command with - in order to ignore the failure of the kill-session command when restarting (because the server is no longer running by then).



                ExecStop=-/usr/bin/tmux kill-session -t %u





                share|improve this answer












                tmux has an option exit-unattached which says If enabled, the server will exit when there are no attached clients, which you can disable with



                set-option -s exit-unattached off


                in your ~/.tmux.conf, but this doesn't seem to have any effect for me (on
                or off), or I have misunderstood what it means.



                You can ask systemd to restart your service on exit by adding the line



                Restart=on-success


                You also need to edit the ExecStop to prefix the command with - in order to ignore the failure of the kill-session command when restarting (because the server is no longer running by then).



                ExecStop=-/usr/bin/tmux kill-session -t %u






                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Dec 16 at 14:37









                meuh

                31.4k11854




                31.4k11854



























                    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%2f488043%2fhow-can-i-leave-the-tmux-server-running-after-the-last-session-exists%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

                    Peggy Mitchell

                    Palaiologos

                    The Forum (Inglewood, California)