Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I issued the ^z; bg; disown sequence in order to allow me to close an ssh session in which I am running a super-important long-running process. This process writes status output to stderr, and it has continued to do so even after being detached (verified with lsof, the stderr fd is open for r/w).

Is there a way to determine that the process has indeed been disowned (will not recv SIGHUP if the shell recvs one)?

share|improve this question
I wonder if this needs to go to – Rilindo Dec 1 '11 at 21:49
Just curious, why not: $PROCESS 1>>/root/std.out 2>>/root/err.out & – Avery Payne Dec 1 '11 at 21:54
up vote 8 down vote accepted

In Bash, the disown command issued by itself will remove backgrounded (via bg or &) processes from the active job table, and mark them to not receive a SIGHUP on logout.

You can also pass one or more jobs to disown, like disown 1 3. The disown -h flag is useful if you want to keep jobs in the table, but still not SIGHUP on logout.

You can view the job table by issuing the jobs command. After a successful background, it will show [1]+ command &. After disowning a job, it should no longer display in the job table, and no longer be killed on logout. You can still view the process via ps ux, top, and other process-viewing utilities.

After a job has been disowned, you can wait for it to terminate naturally or send a signal via kill to the PID to stop it.

Because Bash is just removing the job from the list of running jobs to terminate and the file handles to your terminal's stdout and stderr are still open, you will continue to receive output from the job until your terminal device is closed (when you log out).


# we start a command in the background
$ cat /dev/urandom > test &
[1] 18533

# we see our command is still running
$ jobs
[1]+  Running                 cat /dev/urandom > test &

# we disown the backgrounded job
$ disown 1

# notice it is no longer in the job table
$ jobs

I usually only use disown if I run a potentially long-running command like a rsync or cp and afterwards decide I need to log out without terminating it. If you know you're going to run a command and log out, you can capture the output by piping or teeing it to a file, running it with nohup, or running it in screen (which allows you to retake ownership of the command/terminate afterwards).


# capture stdout and stderr to separate logs
cat /dev/urandom >stdout.log 2>stderr.log

# capture stdout and stderr to the same log, and display to stdout as well
cat /dev/urandom 2>&1 | tee output.log

# run a command under nohup (doesn't require a disown or job control support)
nohup cat /dev/urandom </dev/null
share|improve this answer
+1 Informative and with examples. Nice! – Andy Smith Dec 2 '11 at 0:55
Very informative comment; are you saying that it is not possible to verify a process's detachment (besides noting that it no longer exists in the jobs table)? – mikewaters Dec 2 '11 at 12:17
when you run detach on a backgrounded job, it's going to be detached :) there's not really a middle ground there where running it on a backgrounded process will do nothing. checking jobs just verifies you didn't try to detach a stopped process or something. – lunixbochs Dec 2 '11 at 13:36

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.