Exit shell with shortcut (not typing exit) that closes session properly2019 Community Moderator ElectionWhy does Ctrl-D (EOF) exit the shell?ksh - map Ctrl-D to exit shellHow to exit out of the shell script successfully so that python subprocess think it is successfull exit?Bash script for scp interpreting tilde (~) too soonGUI terminals(?) reset $SHELLCross-session duplicate removal in bash command historyhow to write own shell that works with sshHow to account for shell-session env vars, contexts with chrootAny command in my terminal that exits with non-zero code closes my terminal windowHere-document not working properly on shell scriptHow to properly write and execute a shell script and exit correctly?Securely Piping String in Local Text File to Remote Command using SSH

Difficulty understanding group delay concept

PTIJ: Which Dr. Seuss books should one obtain?

How can I create URL shortcuts/redirects for task/diff IDs in Phabricator?

Would mining huge amounts of resources on the Moon change its orbit?

Imaginary part of expression too difficult to calculate

Air travel with refrigerated insulin

Is "inadequate referencing" a euphemism for plagiarism?

Someone scrambled my calling sign- who am I?

What is the difference between something being completely legal and being completely decriminalized?

Exposing a company lying about themselves in a tightly knit industry: Is my career at risk on the long run?

Justification failure in beamer enumerate list

Extraneous elements in "Europe countries" list

Emojional cryptic crossword

Friend wants my recommendation but I don't want to

Is xar preinstalled on macOS?

Why doesn't the chatan sign the ketubah?

Would this string work as string?

Hackerrank All Women's Codesprint 2019: Name the Product

Why is "la Gestapo" feminine?

How do you justify more code being written by following clean code practices?

Does the Shadow Magic sorcerer's Eyes of the Dark feature work on all Darkness spells or just his/her own?

How can a new country break out from a developed country without war?

Error in master's thesis, I do not know what to do

Animating wave motion in water



Exit shell with shortcut (not typing exit) that closes session properly



2019 Community Moderator ElectionWhy does Ctrl-D (EOF) exit the shell?ksh - map Ctrl-D to exit shellHow to exit out of the shell script successfully so that python subprocess think it is successfull exit?Bash script for scp interpreting tilde (~) too soonGUI terminals(?) reset $SHELLCross-session duplicate removal in bash command historyhow to write own shell that works with sshHow to account for shell-session env vars, contexts with chrootAny command in my terminal that exits with non-zero code closes my terminal windowHere-document not working properly on shell scriptHow to properly write and execute a shell script and exit correctly?Securely Piping String in Local Text File to Remote Command using SSH










8















I use a ProxyJump command for a number of ssh sessions I use daily, and also switch users a lot on these sessions and having to type exit 3 or 4 times in a row isn't too fun.



I am aware of newline + ~ + . to terminate an ssh session, I still have to check if it terminates it amicably like an exit would, but how do you exit all sessions in the current shell with a single command or shortcut such that typing exit 3 or 4 times in my case becomes a one-time thing?










share|improve this question

















  • 1





    ~. just disconnects your SSH client (it's useful when the network has disappeared, for example). Normally, the SSH daemon will recognise that and signal its session with SIGHUP, so it's not quite the same as quitting the shell normally (but it's useful if you can't get any response from the shell).

    – Toby Speight
    7 hours ago















8















I use a ProxyJump command for a number of ssh sessions I use daily, and also switch users a lot on these sessions and having to type exit 3 or 4 times in a row isn't too fun.



I am aware of newline + ~ + . to terminate an ssh session, I still have to check if it terminates it amicably like an exit would, but how do you exit all sessions in the current shell with a single command or shortcut such that typing exit 3 or 4 times in my case becomes a one-time thing?










share|improve this question

















  • 1





    ~. just disconnects your SSH client (it's useful when the network has disappeared, for example). Normally, the SSH daemon will recognise that and signal its session with SIGHUP, so it's not quite the same as quitting the shell normally (but it's useful if you can't get any response from the shell).

    – Toby Speight
    7 hours ago













8












8








8








I use a ProxyJump command for a number of ssh sessions I use daily, and also switch users a lot on these sessions and having to type exit 3 or 4 times in a row isn't too fun.



I am aware of newline + ~ + . to terminate an ssh session, I still have to check if it terminates it amicably like an exit would, but how do you exit all sessions in the current shell with a single command or shortcut such that typing exit 3 or 4 times in my case becomes a one-time thing?










share|improve this question














I use a ProxyJump command for a number of ssh sessions I use daily, and also switch users a lot on these sessions and having to type exit 3 or 4 times in a row isn't too fun.



I am aware of newline + ~ + . to terminate an ssh session, I still have to check if it terminates it amicably like an exit would, but how do you exit all sessions in the current shell with a single command or shortcut such that typing exit 3 or 4 times in my case becomes a one-time thing?







bash shell session






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked 8 hours ago









tsujptsujp

30329




30329







  • 1





    ~. just disconnects your SSH client (it's useful when the network has disappeared, for example). Normally, the SSH daemon will recognise that and signal its session with SIGHUP, so it's not quite the same as quitting the shell normally (but it's useful if you can't get any response from the shell).

    – Toby Speight
    7 hours ago












  • 1





    ~. just disconnects your SSH client (it's useful when the network has disappeared, for example). Normally, the SSH daemon will recognise that and signal its session with SIGHUP, so it's not quite the same as quitting the shell normally (but it's useful if you can't get any response from the shell).

    – Toby Speight
    7 hours ago







1




1





~. just disconnects your SSH client (it's useful when the network has disappeared, for example). Normally, the SSH daemon will recognise that and signal its session with SIGHUP, so it's not quite the same as quitting the shell normally (but it's useful if you can't get any response from the shell).

– Toby Speight
7 hours ago





~. just disconnects your SSH client (it's useful when the network has disappeared, for example). Normally, the SSH daemon will recognise that and signal its session with SIGHUP, so it's not quite the same as quitting the shell normally (but it's useful if you can't get any response from the shell).

– Toby Speight
7 hours ago










2 Answers
2






active

oldest

votes


















17














Ctrl-D will exit a shell in many cases. It is quicker than typing exit Enter. It's still not a single command to terminate everything, but holding Ctrl and hitting D several times is easier and faster. Not sure how valuable this is for your use case.



Discussed in detail here.






share|improve this answer




















  • 2





    The next stop is unix.stackexchange.com/a/182071/5132 , and the stop after that is the further reading there. (-:

    – JdeBP
    8 hours ago











  • Be careful with CTRL+D. In bash, if you have input any characters in your prompt, hitting CTRL+D will execute it the same way Enter would. In other words, don’t type out an rm command and then hit CTRL+D if you didn’t want to execute it. I don’t see this behavior in ksh.

    – Peschke
    6 hours ago







  • 1





    @Peschke On every system I've ever used Ctrl+D does nothing if I've typed something. I've never seen the behavior you describe.

    – John Kugelman
    5 hours ago











  • @JohnKugelman I tested and confirmed the behavior at the time of my comment with bash on RHEL 7.5.

    – Peschke
    5 hours ago


















0














Typing ~. actually does the trick of closing all the "nested" connections through to the deepest.



It does so with the amicable exit you want as long as all your shells are configured to handle SIGHUP as a graceful death. Bash does so by default. You can easily check the amicable exit for your set-up by e.g. seeing whether the .bash_history files of your deeper sessions get properly updated after the ~., or if you set your bash-es not to update .bash_history upon exit then you might set a trap on the EXIT event (or in your ~/.bash_logout) with a command that writes something somewhere and later see whether it got executed.



Besides, I’m not sure what you mean by "exit all sessions in current shell". Each interactive bash is just one session, and the commands you type go always only to the deepest shell of the ProxyJump chain. If you meant "the background jobs in the current shell", bash does send SIGHUP to all its jobs on receiving SIGHUP by the ssh daemon upon the ~. , therefore such exit should be fully amicable if those running jobs react properly to a SIGHUP.






share|improve this answer








New contributor




LL3 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.



















    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%2f507011%2fexit-shell-with-shortcut-not-typing-exit-that-closes-session-properly%23new-answer', 'question_page');

    );

    Post as a guest















    Required, but never shown

























    2 Answers
    2






    active

    oldest

    votes








    2 Answers
    2






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    17














    Ctrl-D will exit a shell in many cases. It is quicker than typing exit Enter. It's still not a single command to terminate everything, but holding Ctrl and hitting D several times is easier and faster. Not sure how valuable this is for your use case.



    Discussed in detail here.






    share|improve this answer




















    • 2





      The next stop is unix.stackexchange.com/a/182071/5132 , and the stop after that is the further reading there. (-:

      – JdeBP
      8 hours ago











    • Be careful with CTRL+D. In bash, if you have input any characters in your prompt, hitting CTRL+D will execute it the same way Enter would. In other words, don’t type out an rm command and then hit CTRL+D if you didn’t want to execute it. I don’t see this behavior in ksh.

      – Peschke
      6 hours ago







    • 1





      @Peschke On every system I've ever used Ctrl+D does nothing if I've typed something. I've never seen the behavior you describe.

      – John Kugelman
      5 hours ago











    • @JohnKugelman I tested and confirmed the behavior at the time of my comment with bash on RHEL 7.5.

      – Peschke
      5 hours ago















    17














    Ctrl-D will exit a shell in many cases. It is quicker than typing exit Enter. It's still not a single command to terminate everything, but holding Ctrl and hitting D several times is easier and faster. Not sure how valuable this is for your use case.



    Discussed in detail here.






    share|improve this answer




















    • 2





      The next stop is unix.stackexchange.com/a/182071/5132 , and the stop after that is the further reading there. (-:

      – JdeBP
      8 hours ago











    • Be careful with CTRL+D. In bash, if you have input any characters in your prompt, hitting CTRL+D will execute it the same way Enter would. In other words, don’t type out an rm command and then hit CTRL+D if you didn’t want to execute it. I don’t see this behavior in ksh.

      – Peschke
      6 hours ago







    • 1





      @Peschke On every system I've ever used Ctrl+D does nothing if I've typed something. I've never seen the behavior you describe.

      – John Kugelman
      5 hours ago











    • @JohnKugelman I tested and confirmed the behavior at the time of my comment with bash on RHEL 7.5.

      – Peschke
      5 hours ago













    17












    17








    17







    Ctrl-D will exit a shell in many cases. It is quicker than typing exit Enter. It's still not a single command to terminate everything, but holding Ctrl and hitting D several times is easier and faster. Not sure how valuable this is for your use case.



    Discussed in detail here.






    share|improve this answer















    Ctrl-D will exit a shell in many cases. It is quicker than typing exit Enter. It's still not a single command to terminate everything, but holding Ctrl and hitting D several times is easier and faster. Not sure how valuable this is for your use case.



    Discussed in detail here.







    share|improve this answer














    share|improve this answer



    share|improve this answer








    edited 8 hours ago









    DopeGhoti

    46.3k56089




    46.3k56089










    answered 8 hours ago









    0xSheepdog0xSheepdog

    1,4171724




    1,4171724







    • 2





      The next stop is unix.stackexchange.com/a/182071/5132 , and the stop after that is the further reading there. (-:

      – JdeBP
      8 hours ago











    • Be careful with CTRL+D. In bash, if you have input any characters in your prompt, hitting CTRL+D will execute it the same way Enter would. In other words, don’t type out an rm command and then hit CTRL+D if you didn’t want to execute it. I don’t see this behavior in ksh.

      – Peschke
      6 hours ago







    • 1





      @Peschke On every system I've ever used Ctrl+D does nothing if I've typed something. I've never seen the behavior you describe.

      – John Kugelman
      5 hours ago











    • @JohnKugelman I tested and confirmed the behavior at the time of my comment with bash on RHEL 7.5.

      – Peschke
      5 hours ago












    • 2





      The next stop is unix.stackexchange.com/a/182071/5132 , and the stop after that is the further reading there. (-:

      – JdeBP
      8 hours ago











    • Be careful with CTRL+D. In bash, if you have input any characters in your prompt, hitting CTRL+D will execute it the same way Enter would. In other words, don’t type out an rm command and then hit CTRL+D if you didn’t want to execute it. I don’t see this behavior in ksh.

      – Peschke
      6 hours ago







    • 1





      @Peschke On every system I've ever used Ctrl+D does nothing if I've typed something. I've never seen the behavior you describe.

      – John Kugelman
      5 hours ago











    • @JohnKugelman I tested and confirmed the behavior at the time of my comment with bash on RHEL 7.5.

      – Peschke
      5 hours ago







    2




    2





    The next stop is unix.stackexchange.com/a/182071/5132 , and the stop after that is the further reading there. (-:

    – JdeBP
    8 hours ago





    The next stop is unix.stackexchange.com/a/182071/5132 , and the stop after that is the further reading there. (-:

    – JdeBP
    8 hours ago













    Be careful with CTRL+D. In bash, if you have input any characters in your prompt, hitting CTRL+D will execute it the same way Enter would. In other words, don’t type out an rm command and then hit CTRL+D if you didn’t want to execute it. I don’t see this behavior in ksh.

    – Peschke
    6 hours ago






    Be careful with CTRL+D. In bash, if you have input any characters in your prompt, hitting CTRL+D will execute it the same way Enter would. In other words, don’t type out an rm command and then hit CTRL+D if you didn’t want to execute it. I don’t see this behavior in ksh.

    – Peschke
    6 hours ago





    1




    1





    @Peschke On every system I've ever used Ctrl+D does nothing if I've typed something. I've never seen the behavior you describe.

    – John Kugelman
    5 hours ago





    @Peschke On every system I've ever used Ctrl+D does nothing if I've typed something. I've never seen the behavior you describe.

    – John Kugelman
    5 hours ago













    @JohnKugelman I tested and confirmed the behavior at the time of my comment with bash on RHEL 7.5.

    – Peschke
    5 hours ago





    @JohnKugelman I tested and confirmed the behavior at the time of my comment with bash on RHEL 7.5.

    – Peschke
    5 hours ago













    0














    Typing ~. actually does the trick of closing all the "nested" connections through to the deepest.



    It does so with the amicable exit you want as long as all your shells are configured to handle SIGHUP as a graceful death. Bash does so by default. You can easily check the amicable exit for your set-up by e.g. seeing whether the .bash_history files of your deeper sessions get properly updated after the ~., or if you set your bash-es not to update .bash_history upon exit then you might set a trap on the EXIT event (or in your ~/.bash_logout) with a command that writes something somewhere and later see whether it got executed.



    Besides, I’m not sure what you mean by "exit all sessions in current shell". Each interactive bash is just one session, and the commands you type go always only to the deepest shell of the ProxyJump chain. If you meant "the background jobs in the current shell", bash does send SIGHUP to all its jobs on receiving SIGHUP by the ssh daemon upon the ~. , therefore such exit should be fully amicable if those running jobs react properly to a SIGHUP.






    share|improve this answer








    New contributor




    LL3 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
    Check out our Code of Conduct.
























      0














      Typing ~. actually does the trick of closing all the "nested" connections through to the deepest.



      It does so with the amicable exit you want as long as all your shells are configured to handle SIGHUP as a graceful death. Bash does so by default. You can easily check the amicable exit for your set-up by e.g. seeing whether the .bash_history files of your deeper sessions get properly updated after the ~., or if you set your bash-es not to update .bash_history upon exit then you might set a trap on the EXIT event (or in your ~/.bash_logout) with a command that writes something somewhere and later see whether it got executed.



      Besides, I’m not sure what you mean by "exit all sessions in current shell". Each interactive bash is just one session, and the commands you type go always only to the deepest shell of the ProxyJump chain. If you meant "the background jobs in the current shell", bash does send SIGHUP to all its jobs on receiving SIGHUP by the ssh daemon upon the ~. , therefore such exit should be fully amicable if those running jobs react properly to a SIGHUP.






      share|improve this answer








      New contributor




      LL3 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.






















        0












        0








        0







        Typing ~. actually does the trick of closing all the "nested" connections through to the deepest.



        It does so with the amicable exit you want as long as all your shells are configured to handle SIGHUP as a graceful death. Bash does so by default. You can easily check the amicable exit for your set-up by e.g. seeing whether the .bash_history files of your deeper sessions get properly updated after the ~., or if you set your bash-es not to update .bash_history upon exit then you might set a trap on the EXIT event (or in your ~/.bash_logout) with a command that writes something somewhere and later see whether it got executed.



        Besides, I’m not sure what you mean by "exit all sessions in current shell". Each interactive bash is just one session, and the commands you type go always only to the deepest shell of the ProxyJump chain. If you meant "the background jobs in the current shell", bash does send SIGHUP to all its jobs on receiving SIGHUP by the ssh daemon upon the ~. , therefore such exit should be fully amicable if those running jobs react properly to a SIGHUP.






        share|improve this answer








        New contributor




        LL3 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
        Check out our Code of Conduct.










        Typing ~. actually does the trick of closing all the "nested" connections through to the deepest.



        It does so with the amicable exit you want as long as all your shells are configured to handle SIGHUP as a graceful death. Bash does so by default. You can easily check the amicable exit for your set-up by e.g. seeing whether the .bash_history files of your deeper sessions get properly updated after the ~., or if you set your bash-es not to update .bash_history upon exit then you might set a trap on the EXIT event (or in your ~/.bash_logout) with a command that writes something somewhere and later see whether it got executed.



        Besides, I’m not sure what you mean by "exit all sessions in current shell". Each interactive bash is just one session, and the commands you type go always only to the deepest shell of the ProxyJump chain. If you meant "the background jobs in the current shell", bash does send SIGHUP to all its jobs on receiving SIGHUP by the ssh daemon upon the ~. , therefore such exit should be fully amicable if those running jobs react properly to a SIGHUP.







        share|improve this answer








        New contributor




        LL3 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
        Check out our Code of Conduct.









        share|improve this answer



        share|improve this answer






        New contributor




        LL3 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
        Check out our Code of Conduct.









        answered 6 hours ago









        LL3LL3

        1




        1




        New contributor




        LL3 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
        Check out our Code of Conduct.





        New contributor





        LL3 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
        Check out our Code of Conduct.






        LL3 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
        Check out our Code of Conduct.



























            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.




            draft saved


            draft discarded














            StackExchange.ready(
            function ()
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f507011%2fexit-shell-with-shortcut-not-typing-exit-that-closes-session-properly%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

            How to create a command for the “strange m” symbol in latex? Announcing the arrival of Valued Associate #679: Cesar Manara Planned maintenance scheduled April 23, 2019 at 23:30 UTC (7:30pm US/Eastern)How do you make your own symbol when Detexify fails?Writing bold small caps with mathpazo packageplus-minus symbol with parenthesis around the minus signGreek character in Beamer document titleHow to create dashed right arrow over symbol?Currency symbol: Turkish LiraDouble prec as a single symbol?Plus Sign Too Big; How to Call adfbullet?Is there a TeX macro for three-legged pi?How do I get my integral-like symbol to align like the integral?How to selectively substitute a letter with another symbol representing the same letterHow do I generate a less than symbol and vertical bar that are the same height?

            Българска екзархия Съдържание История | Български екзарси | Вижте също | Външни препратки | Литература | Бележки | НавигацияУстав за управлението на българската екзархия. Цариград, 1870Слово на Ловешкия митрополит Иларион при откриването на Българския народен събор в Цариград на 23. II. 1870 г.Българската правда и гръцката кривда. От С. М. (= Софийски Мелетий). Цариград, 1872Предстоятели на Българската екзархияПодмененият ВеликденИнформационна агенция „Фокус“Димитър Ризов. Българите в техните исторически, етнографически и политически граници (Атлас съдържащ 40 карти). Berlin, Königliche Hoflithographie, Hof-Buch- und -Steindruckerei Wilhelm Greve, 1917Report of the International Commission to Inquire into the Causes and Conduct of the Balkan Wars

            Category:Tremithousa Media in category "Tremithousa"Navigation menuUpload media34° 49′ 02.7″ N, 32° 26′ 37.32″ EOpenStreetMapGoogle EarthProximityramaReasonatorScholiaStatisticsWikiShootMe