How to maintain a command from terminal running? [duplicate]

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











up vote
0
down vote

favorite













This question already has an answer here:



  • Keep SSH Sessions running after disconnection

    8 answers



I launch connexion ssh to use rsync command in terminal and I would like to shutdown my computer, but I need to let run the process rsync.



I executed this command on a remote host. If I quit now then the process will stop I guess?



Yes I know I should run my command with option to avoid to lost the process.







share|improve this question













marked as duplicate by Kiwy, vonbrand, Romeo Ninov, Jeff Schaller, Timothy Martin Apr 27 at 21:12


This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.














  • how did you launch the command remotely? ssh?
    – Sufiyan Ghori
    Apr 27 at 11:43










  • What exact command? How was it executed - over SSH? Add details.
    – Vlastimil
    Apr 27 at 12:11










  • The typical way of managing this is to use screen(1).
    – vonbrand
    Apr 27 at 13:42










  • @Sufiyan Ghori yes I use ssh then I use rsync
    – DragonF0rce
    Apr 27 at 15:51










  • Look into using nohup, or screen, perhaps.
    – mrflash818
    Apr 27 at 16:02














up vote
0
down vote

favorite













This question already has an answer here:



  • Keep SSH Sessions running after disconnection

    8 answers



I launch connexion ssh to use rsync command in terminal and I would like to shutdown my computer, but I need to let run the process rsync.



I executed this command on a remote host. If I quit now then the process will stop I guess?



Yes I know I should run my command with option to avoid to lost the process.







share|improve this question













marked as duplicate by Kiwy, vonbrand, Romeo Ninov, Jeff Schaller, Timothy Martin Apr 27 at 21:12


This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.














  • how did you launch the command remotely? ssh?
    – Sufiyan Ghori
    Apr 27 at 11:43










  • What exact command? How was it executed - over SSH? Add details.
    – Vlastimil
    Apr 27 at 12:11










  • The typical way of managing this is to use screen(1).
    – vonbrand
    Apr 27 at 13:42










  • @Sufiyan Ghori yes I use ssh then I use rsync
    – DragonF0rce
    Apr 27 at 15:51










  • Look into using nohup, or screen, perhaps.
    – mrflash818
    Apr 27 at 16:02












up vote
0
down vote

favorite









up vote
0
down vote

favorite












This question already has an answer here:



  • Keep SSH Sessions running after disconnection

    8 answers



I launch connexion ssh to use rsync command in terminal and I would like to shutdown my computer, but I need to let run the process rsync.



I executed this command on a remote host. If I quit now then the process will stop I guess?



Yes I know I should run my command with option to avoid to lost the process.







share|improve this question














This question already has an answer here:



  • Keep SSH Sessions running after disconnection

    8 answers



I launch connexion ssh to use rsync command in terminal and I would like to shutdown my computer, but I need to let run the process rsync.



I executed this command on a remote host. If I quit now then the process will stop I guess?



Yes I know I should run my command with option to avoid to lost the process.





This question already has an answer here:



  • Keep SSH Sessions running after disconnection

    8 answers









share|improve this question












share|improve this question




share|improve this question








edited Apr 27 at 15:50
























asked Apr 27 at 11:39









DragonF0rce

12




12




marked as duplicate by Kiwy, vonbrand, Romeo Ninov, Jeff Schaller, Timothy Martin Apr 27 at 21:12


This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.






marked as duplicate by Kiwy, vonbrand, Romeo Ninov, Jeff Schaller, Timothy Martin Apr 27 at 21:12


This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.













  • how did you launch the command remotely? ssh?
    – Sufiyan Ghori
    Apr 27 at 11:43










  • What exact command? How was it executed - over SSH? Add details.
    – Vlastimil
    Apr 27 at 12:11










  • The typical way of managing this is to use screen(1).
    – vonbrand
    Apr 27 at 13:42










  • @Sufiyan Ghori yes I use ssh then I use rsync
    – DragonF0rce
    Apr 27 at 15:51










  • Look into using nohup, or screen, perhaps.
    – mrflash818
    Apr 27 at 16:02
















  • how did you launch the command remotely? ssh?
    – Sufiyan Ghori
    Apr 27 at 11:43










  • What exact command? How was it executed - over SSH? Add details.
    – Vlastimil
    Apr 27 at 12:11










  • The typical way of managing this is to use screen(1).
    – vonbrand
    Apr 27 at 13:42










  • @Sufiyan Ghori yes I use ssh then I use rsync
    – DragonF0rce
    Apr 27 at 15:51










  • Look into using nohup, or screen, perhaps.
    – mrflash818
    Apr 27 at 16:02















how did you launch the command remotely? ssh?
– Sufiyan Ghori
Apr 27 at 11:43




how did you launch the command remotely? ssh?
– Sufiyan Ghori
Apr 27 at 11:43












What exact command? How was it executed - over SSH? Add details.
– Vlastimil
Apr 27 at 12:11




What exact command? How was it executed - over SSH? Add details.
– Vlastimil
Apr 27 at 12:11












The typical way of managing this is to use screen(1).
– vonbrand
Apr 27 at 13:42




The typical way of managing this is to use screen(1).
– vonbrand
Apr 27 at 13:42












@Sufiyan Ghori yes I use ssh then I use rsync
– DragonF0rce
Apr 27 at 15:51




@Sufiyan Ghori yes I use ssh then I use rsync
– DragonF0rce
Apr 27 at 15:51












Look into using nohup, or screen, perhaps.
– mrflash818
Apr 27 at 16:02




Look into using nohup, or screen, perhaps.
– mrflash818
Apr 27 at 16:02










2 Answers
2






active

oldest

votes

















up vote
2
down vote













You can run disown -a && exit which will release all the shell processes you have started from the current shell and end the current shell. The processes will continue to run.






share|improve this answer




























    up vote
    1
    down vote













    It is very generic, and there are many solution.



    You can use nohup. But often on remote host a screen (or tmux) is used.



    On the first case: process continue also if terminal is terminated (but you should no more use stdin/stout/stderr (a redirect it is ok).



    On the second, it is just a virtual terminal, so you can return (from an other computer) and see the terminal.






    share|improve this answer





















    • The command is running and I cant stop it now so there is a way to maintain the PID ?
      – DragonF0rce
      Apr 27 at 11:56










    • Now it is late. I use the other tools, so I do not know.
      – Giacomo Catenazzi
      Apr 27 at 12:03

















    2 Answers
    2






    active

    oldest

    votes








    2 Answers
    2






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes








    up vote
    2
    down vote













    You can run disown -a && exit which will release all the shell processes you have started from the current shell and end the current shell. The processes will continue to run.






    share|improve this answer

























      up vote
      2
      down vote













      You can run disown -a && exit which will release all the shell processes you have started from the current shell and end the current shell. The processes will continue to run.






      share|improve this answer























        up vote
        2
        down vote










        up vote
        2
        down vote









        You can run disown -a && exit which will release all the shell processes you have started from the current shell and end the current shell. The processes will continue to run.






        share|improve this answer













        You can run disown -a && exit which will release all the shell processes you have started from the current shell and end the current shell. The processes will continue to run.







        share|improve this answer













        share|improve this answer



        share|improve this answer











        answered Apr 27 at 11:52









        chevallier

        8351116




        8351116






















            up vote
            1
            down vote













            It is very generic, and there are many solution.



            You can use nohup. But often on remote host a screen (or tmux) is used.



            On the first case: process continue also if terminal is terminated (but you should no more use stdin/stout/stderr (a redirect it is ok).



            On the second, it is just a virtual terminal, so you can return (from an other computer) and see the terminal.






            share|improve this answer





















            • The command is running and I cant stop it now so there is a way to maintain the PID ?
              – DragonF0rce
              Apr 27 at 11:56










            • Now it is late. I use the other tools, so I do not know.
              – Giacomo Catenazzi
              Apr 27 at 12:03














            up vote
            1
            down vote













            It is very generic, and there are many solution.



            You can use nohup. But often on remote host a screen (or tmux) is used.



            On the first case: process continue also if terminal is terminated (but you should no more use stdin/stout/stderr (a redirect it is ok).



            On the second, it is just a virtual terminal, so you can return (from an other computer) and see the terminal.






            share|improve this answer





















            • The command is running and I cant stop it now so there is a way to maintain the PID ?
              – DragonF0rce
              Apr 27 at 11:56










            • Now it is late. I use the other tools, so I do not know.
              – Giacomo Catenazzi
              Apr 27 at 12:03












            up vote
            1
            down vote










            up vote
            1
            down vote









            It is very generic, and there are many solution.



            You can use nohup. But often on remote host a screen (or tmux) is used.



            On the first case: process continue also if terminal is terminated (but you should no more use stdin/stout/stderr (a redirect it is ok).



            On the second, it is just a virtual terminal, so you can return (from an other computer) and see the terminal.






            share|improve this answer













            It is very generic, and there are many solution.



            You can use nohup. But often on remote host a screen (or tmux) is used.



            On the first case: process continue also if terminal is terminated (but you should no more use stdin/stout/stderr (a redirect it is ok).



            On the second, it is just a virtual terminal, so you can return (from an other computer) and see the terminal.







            share|improve this answer













            share|improve this answer



            share|improve this answer











            answered Apr 27 at 11:46









            Giacomo Catenazzi

            1,973314




            1,973314











            • The command is running and I cant stop it now so there is a way to maintain the PID ?
              – DragonF0rce
              Apr 27 at 11:56










            • Now it is late. I use the other tools, so I do not know.
              – Giacomo Catenazzi
              Apr 27 at 12:03
















            • The command is running and I cant stop it now so there is a way to maintain the PID ?
              – DragonF0rce
              Apr 27 at 11:56










            • Now it is late. I use the other tools, so I do not know.
              – Giacomo Catenazzi
              Apr 27 at 12:03















            The command is running and I cant stop it now so there is a way to maintain the PID ?
            – DragonF0rce
            Apr 27 at 11:56




            The command is running and I cant stop it now so there is a way to maintain the PID ?
            – DragonF0rce
            Apr 27 at 11:56












            Now it is late. I use the other tools, so I do not know.
            – Giacomo Catenazzi
            Apr 27 at 12:03




            Now it is late. I use the other tools, so I do not know.
            – Giacomo Catenazzi
            Apr 27 at 12:03


            Popular posts from this blog

            How to check contact read email or not when send email to Individual?

            Bahrain

            Postfix configuration issue with fips on centos 7; mailgun relay