Today, Benjamin Scott gleaned this insight:
> What Kevin D. Clark <[EMAIL PROTECTED]> said about this is generally
> correct (that you can't "release" a process from a terminal). (I consider
> this a design flaw in Unix.)
>
> However, most X programs seem to handle the situation you describe without
> trouble. I'm not sure if this is because they deliberately set the SIGHUP
> signal to be ignored, or if they don't use terminal I/O and thus don't
> encounter the problem, or what, but I routinely open a terminal, issue
> "netscape &", and then close the terminal, without problems.
You must be using some alien version of netscape then... I typically do
this by accident only to find that netscape goes off to another plane of
existence, and can be killed only by a SIGKILL. Though at least sending
it a SIGTERM will get it to clean up after itself, most of the time (i.e.
removing the lock files)... I've seen this behavior on several Linux
distributions and IIRC on DEC Unix running on alpha workstations too.
--
PGP/GPG Public key at http://cerberus.ne.mediaone.net/~derek/pubkey.txt
------------------------------------------------------
Derek D. Martin | Unix/Linux Geek
[EMAIL PROTECTED] | [EMAIL PROTECTED]
------------------------------------------------------
**********************************************************
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
**********************************************************
