Well, I started a long-running compile on my Pi...in an SSH session. Is it safe to close the session? I'm actually not sure.
@Skirmisher either you cancel it and run it in a 'screen' session instead, or you hit ctrl+z to pause it, then type 'bg' to run it in the background, then 'nohup' to disown it. you won't see the output when doing the latter so I'd recommend screen when possible. screen is kinda unintuitive to use at first but you can find guides
@notwa Wait, how do I use nohup on a running process? If I don't, does the process still die if I close the session?
@Skirmisher oh no wait, i meant 'disown', sorry! i put too much thought into it…
@notwa Turns out bash is configured by default to not send SIGHUP to running jobs when a shell exits. Anyway, I guess I'll let this go and scream at it in the morning when the compile inevitably fails, or something.
@notwa Wait, once all of my sessions logged out, then it did die. Oh well, all the objects are still there, so the make should pick up where it left off. Whatever.
@Skirmisher also yeah, background processes close with your session. your shell might even warn you about it, i know zsh does.