Computer shutdown during a mv command over SSH. Of course mv doesn't delete the old directory until all the files are moved (have always known/thought this applied to both Linux and Windows) so everything is good.

Am right in assuming that if an SSH sessions disconnects that any given command being performed ends as well?

It is my understanding that it does, as the terminal closes.

As an alternative, you can use something like tmux or screen, which allows you to start a remote terminal session and disconnect from and reconnect to it without the terminal's closing.

I would expect both of them to be in your repos.

Normally, when SSH closes the processes get sent a SIGHUP signal (actually two in short order) and then do with that what they will. The normal reaction is to stop.

If you don't write your program to trap and process SIGHUP you can use nohup to protect a single process or, as mentioned already, tmux or screen. I prefer tmux of the two and now use it almost exclusively over screen even though I'd been using the latter for many years.

systemd is said to break all of that, starting last year. Though some distros are also said to have deployed a work-around to keep the session behavior as expected. Check with your specific distro to see the exact situation on your hands.

"SIGHUP" means "hang-up," as in, "the teletype user hung up the phone."

Ordinarily, the parent process receives this signal and terminates, thus (slight hand-waving here ...) terminating all of the children.

The nohup command can be used to influence this behavior.

Thank you so much for sharing the nohup command. Really neat. Exactly what was looking for. Also happy to see nohup work in terminal on a local machine and not just over SSH. Previously had to leave a teminal window open for FreeFDP but nohup enables the terminal windows to be closed.