[TriLUG] nohup (unattended jobs/processes)

[Bradford Powell]

As others have mentioned, screen is definately the way to go, but since
you've already started this process and don't want to stop it in order to
run it under screen...

If the process is running under bash, you can use the 'disown'
shell-builtin (see the manpage for bash or `help disown`). I usually just
type `disown %1` after having backgrounded a job. Of course, this is
before I found out about the glories of screen.

I'm not sure what facilities other shells may have for doing something
like this. Basically you have to tell the shell to remove the process from
the list of jobs to be exited when the shell is exited.

-- Bradford Powell
-- bradford_powell at unc.edu

On Tue, 5 Aug 2003, Jeff Bollinger wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> I started a process yesterday that I believe will take a few more days
> to complete.  I'm logged into my Gnome desktop, and have ssh'd into
> another host where I'm running the job.  I'm a little nervous now that
> my SSH connection may drop/system will crash/other catastrophes could
> happen, so I would like to know if its possible to use something like
> `nohup` now that the job has already started, so that if anything
> happens to my connection, the job will continue until complete.  It's
> currently running in the background at this point, but now that it's
> started can I modify it?
> 
> Thanks,
> Jeff