Warren Mansur writes:
> Is there a way to release all processes that were run from a terminal window
> (that is, after they are already running), so they won't be closed when you close
> the terminal?
Not in general, no.
> If that's not possible, is there a way to release a specific
> process after it's already running?
Not in general, no.
The thing that is going on here is that these processes are being sent
the SIGHUP signal when the parent shell exits. By default, the
disposition of a process is to exit when this happens.
All nohup does is to modify this disposition such that SIGHUP signals
are ignored (via SIG_IGN). This disposition is preserved across the
call to exec() which invokes the real program that you wanted to run.
Oh, and once a process is running, it is free to modify the signal
handling dispositions even further.
Once you've started running a program (like, for example, "find"),
unless you've made arrangements beforehand, it's nearly impossible to
modify the signal handling characteristics of a running process.
--kevin
--
Kevin D. Clark | |
[EMAIL PROTECTED] | [EMAIL PROTECTED] | Give me a decent UNIX
Enterasys Networks | PGP Key Available | and I can move the world
Durham, N.H. (USA) | |
**********************************************************
To unsubscribe from this list, send mail to
[EMAIL PROTECTED] with the following text in the
*body* (*not* the subject line) of the letter:
unsubscribe gnhlug
**********************************************************
