Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

3
  • 9
    See also Can I nohup/screen an already-started process? and Resume command running in dropped SSH session, which mention several ptrace-based solutions not (currently) mentioned here. Commented Nov 15, 2010 at 22:47
  • 1
    From questions like unix.stackexchange.com/a/4039/13496 I'm hearing about retty and neercs. Hmmm... wonder if there's smth like a "screen here" layer before I run a process next time should I lose the top terminal in the future, that will make it easy to snap back in the stdin/out/err Commented Mar 8, 2012 at 15:00
  • The secondary/implicit issue in this question I can't fathom is...why did the shell choose to disown a suspended job when there is a newer/just launched one in background that doesn't even need/wait for stdin? This is the treatment I've gotten used to so don't know what went different here... Commented Mar 11, 2012 at 13:54