What's the difference between nohup foocommand
and nohup foocommand &
?
I understand that &
marks the task/job/process as running in the background but does that make it more resilient than it would otherwise be?
What happens in both scenarios if my SSH session timeouts or if I get disconnected?