Since nobody has said yet, I use screen pretty heavily. Want to run a long running task, starting it from your phone? Run screen to create a detachable session then the long running command. You can then safely close out of your terminal or detach with ctrl a, d and continue in your terminal doing something else. screen -r to get back to it.
Eyyy, don’t hate, this is how I start all my work programs. That command is really nice and creates all work programs as children of a single terminal session for easy closing later.
How does screen / tmux work when detached from a session, how does it keep the session alive (both when running locally, and while ssh:ing to a server)? Is there a daemon involved?
Since nobody has said yet, I use screen pretty heavily. Want to run a long running task, starting it from your phone? Run screen to create a detachable session then the long running command. You can then safely close out of your terminal or detach with ctrl a, d and continue in your terminal doing something else. screen -r to get back to it.
In a similar vein,
nohuplets you send tasks to the background and seems to be everywhere.You can’t mention
nohupwithout at least mentioningkill -9orpkillto slay the monster you created you madmanSometimes I’ll just reboot the entire damn machine just to be safe ;)
shutdown -r nowEyyy, don’t hate, this is how I start all my work programs. That command is really nice and creates all work programs as children of a single terminal session for easy closing later.
No hate! Just need to make sure people know so they don’t create a bazillion threads without realizing it, or how to stop them effectively
Also, screen can connect to an UART device or serial or anything that offers up a TTY
Don’t use
screen, but I do usetmuxpretty heavily.I Always forget to run screen first, so I just rely heavily on dtach
Simply change your terminal command to execute the terminal multiplexer of your choice.
man terminal_of_choice, look for (start) command.No thanks, I’m good
How does screen / tmux work when detached from a session, how does it keep the session alive (both when running locally, and while ssh:ing to a server)? Is there a daemon involved?
You can find out by running screen and executing pstree, that way you can see how the screen process is run.