Resume command running in dropped SSH session
Attempting to connect a new terminal's current STD* file descriptors to an old running process is just asking for trouble. Even if you do manage to do that, the terminal's job control won't work as expected. You'll have a mess left behind if you eventually exit the taken-over program, and what happens to the shell that sacrificed its file descriptors to be handed to the newly-backgrounded process. Will ssh stay open when that shell goes away? Probably not. So you'll need to redirect it somewhere else first.
Possible or not, I'd wager that it's more desirable to just let the abandoned process get killed "naturally". If you're doing anything important enough to justify trying to do all the hackery required to resume control and you're on an unstable link, you should probably know that in advance and just use screen (or vnc, or whatever floats your detached-control boat). :)
I know this is an old question , but I felt it is important to add my findings in case someone else comes across this like I did.
I haven't seen any unusual consequences to doing this yes, but this is what I used and it worked amazingly. Sometimes when we run long processes on our server it will occasionally disconnect the ssh session. The process along with the tty session appears to stay running but we can't reconnect to it. I found the program below to pull the process to the newly connected session.
Here's more info
Generally, the right way to handle this is to prepare for it ahead of time, using GNU
screen or bash's
disown mechanisms. If you are using
tcsh, the shell will disown background jobs when it exits abnormally.
If you aren't using
screen but have managed to keep your process running via one of the disown methods, you might be able to fake reconnecting to the process with
[...] with some dirty hacks, it is not impossible to reopen a process' stdout/stderr/stdin. [...]
And then use gdb for instance to attach to the process, do some call close(0)
call open("/dev/pts/xx", ...)
Now, you'd have to tweak this process for your situation. I doubt it would help if you haven't managed to disown the process. If you're using
bash, see this post about making bash automatically disown background processes on exit (basically, turn off huponexit with shopt). With a foreground process, you need to have used nohup.