awesome video, but please also provide source code in github for bash scripting next time because your way of initiate the tmux quite interesting especially with countdown. Thanks
I will put up the countdown code when I do a video on the script, it's not ready for production. For this video, I have the following: github.com/Inarus899/tmux_example/tree/main
htop displays the parent, child connection with processes, and nohup starts as a child of bash, but when I close bash, it gets inherited by the parent of bash instead of dying. When I run tmux, that session of bash becomes a child of tmux. They both continue after closing the bash window, but in different ways. A combination of nohup, &, and tail -F could be useful in some situations.
Nice video!
awesome video, but please also provide source code in github for bash scripting next time because your way of initiate the tmux quite interesting especially with countdown. Thanks
I will put up the countdown code when I do a video on the script, it's not ready for production. For this video, I have the following:
github.com/Inarus899/tmux_example/tree/main
You said your process dies because it's a child of the ssh session that you close ... Yet tmux is also a child of the ssh session. Perhaps use nohup?
htop displays the parent, child connection with processes, and nohup starts as a child of bash, but when I close bash, it gets inherited by the parent of bash instead of dying. When I run tmux, that session of bash becomes a child of tmux. They both continue after closing the bash window, but in different ways.
A combination of nohup, &, and tail -F could be useful in some situations.