Skip to main content
Unix & Linux

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.

10
  • 4
    after disown how can I again read the stdout of the running process? Commented May 22, 2014 at 10:59
  • 2
    @neckTwi, serverfault.com/questions/55880/… Commented May 22, 2014 at 11:23
  • 2
    @necktwi disown does not disconnect stdout or stderr. However nohup does, as does >/dev/null (disconnect standard out), 2>/dev/null (disconnect standard error). It (disown) disconnects job-control. Commented Jul 21, 2016 at 22:08
  • 3
    To anyone else finding this, this really messed things up for me so be careful. Ctrl+z stopped it just fine, but bg made it start running again and now it won't respond to Ctrl+Z or Ctrl+C. Now there seems to be no way to exit the running command safely at all. No idea why, just did exactly what it said, but for whatever reason bg bought it back running. I can't do the next step of typing disown because there's too much output to type anything. Commented Sep 20, 2017 at 15:47
  • 3
    @JohnMellor You were probably running into a similar situation to ctrl-alt-delor's comment, where the program is indeed running in the background but still has its stdout piped to your shell. Ctrl + C and Ctrl + Z won't do anything from here because no program is actually running in the foreground. You can still type in commands from here, like ls or disown without a problem, it is just really hard to read what you're typing while output is being mixed in with your characters. I just had a similar situation with ffmpeg, but it works fine. Commented Jul 22, 2019 at 21:46