If your going to learn a new terminal multiplexer; make it TMUX. TMUX is like screen but is a little more featured, less conflicting key sequences, multi-user support, and more actively developed.
On 02/23/2017 07:59 PM, Tom wrote: > I'd second the use of screen as that will allow you to reconnect with > the shell where you started the command should you need it. > Another alternative to nohup I often use: at -f commandToRun now > The dependency is to start atd.service > The advantages to nohup that is that you will get the command's output > by email, so that you can check the success/failure and what happened. > Another good thing is that you can start your command with delay or at > certain time/date if needed. > Tomas > On Thu, 2017-02-23 at 19:29 -0800, Galen Seitz wrote: >> On 02/23/17 19:18, Rich Shepard wrote: >>> A hydrologic model I need to run has an estimated completion >>> time almost 4 >>> days in the future so I start it in the background by appending '&' >>> to the >>> command line. >>> >>> The problem is when I log out of the system and log in as root >>> that >>> process (actually, there are 3 processes running, one with status >>> Rl the >>> others as S (suspended). >>> >>> Is there an alternative way to have a program keep running after >>> the user >>> invoking it logs off? >> Traditionally this was done using nohup, but screen is probably a >> better >> choice. >> >> <http://tecadmin.net/run-command-in-background-on-linux/> >> (not *the* definitive link, just the first one that seemed to cover >> what >> you were asking) >> >> galen > _______________________________________________ > PLUG mailing list > [email protected] > http://lists.pdxlinux.org/mailman/listinfo/plug _______________________________________________ PLUG mailing list [email protected] http://lists.pdxlinux.org/mailman/listinfo/plug
