Instead of said cleanup, the process is moved to be a child of init instead.
When the last stops, all proceses under it gets cleaned up. This is useful for anyone who who runs long-term jobs, wants to leave work around, has an iffy internet/WiFi connection, wants to leave (text-mode) editors open to continue with tomorrow, or whatnot.Ī program is a child of a shell, that shell is the child of either the graphical terminal, or sshd or such. When said viewer stops, it doesn't affect the processes - they were only ever inputting/outputting to the service. The service connects the input/output streams to that client when you need it. Starting screen/tmux creates that host process, plus an interactive viewer into it.Įach window you start within that service defaults to start its own shell. You can think of screen/tmux as a background service that hosts interactive processes. They run processes separately from the shell you logged in with Switching between them mainly just connects the keyboard/output to specific ones. It means one hosted session can contain many interactive shells side by side, Terminal multiplexing means they can host/view many process at a time. Much of the point is that the process's terminals are tied to the background process, so anything else (SSH connection, viewing terminal) breaking has no effect on the real process One of the most complex cases in too much detail. It's useful for leaving work open, and avoid processes broken by being cleaned up with the terminals they started from.
You can open a shell (sets of them, in a lot of practice) that sticks around, and that you can reconnect to later.
0 kommentar(er)
