UNIX and/or Gosling Emacs problem.

[Shaji Bhaskar]

I have a problem with process handling in Gosling Emacs (V2.01).
running under UNIX 4.2.  What I need to do is to leave a process
running in the background even after Emacs exits.  I start the
process using "start-filtered-process".  I send the process something
on its standard input using a "region-to-process", send an EOF to the
process, and then exit emacs.  However, Emacs kills my process if it
is still running.  Setting the variable "silently-kill-processes" to
0 is supposed to do the trick.  However, Emacs appears to be sending
a SIGHUP to its children regardless.  I do not know whether the
problem is with UNIX pseudo ttys or an EMACS bug, so I am posting
this to both net.unix and net.emacs.  

I have tried explicitly ignoring the signal in my child process, but
it is possible that the process receives the SIGHUP before it does a
signal(SIGHUP, SIG_IGN), leaving me with a dead pocess when I think I
have a running process.  I need a way around this problem that is
elegant.  

Is this a well-known problem?  Are there any easy fixes?  I do not
want to hack the source of Emacs unless it is to remove the bug (if
any) that causes this signal to be sent.  In particular, I dont want
to hack Emacs to create children that ignore SIGHUP, unless the
problem is caused by the operating system's process handling
mechanism, but am willing to try it as a last-ditch measure.

* Yet another reason for switching to GNUEmacs, maybe? :-) *

Shaji Bhaskar, Dept of Comp. Sc., SUNY at Stony Brook.
UUCP : {allegra, philabs}!shaji
CSnet : shaji at sbcs.csnet