First this question is related but definitely not the same as this very nice question:
There’s a wealth of stack exchange answers regarding nohup, here’s a couple for reference:
When do you need ‘nohup’ if you’re already forking using ‘&’?
Why use “nohup &” rather than “exec &”
I want to run a process in background without killing it on shell exit, according to Nohup concept the following command should work until I kill it manually:
I need to execute multiple commands using nohup. Each command should be executed after the previous command.
This question is old, and I am still not clear about why.