Path: utzoo!attcan!uunet!ncrlnk!ncrcae!ece-csc!ncsuvx!lll-winken!csd4.milw.wisc.edu!mailrus!tut.cis.ohio-state.edu!rutgers!psuvax1!vu-vlsi!dsinc!syd
From: syd@dsinc.UUCP (Syd Weinstein)
Newsgroups: comp.mail.elm
Subject: Re: newmail also displays on console (bug)
Message-ID: <92@dsinc.UUCP>
Date: 11 Mar 89 18:29:44 GMT
References: <316@wubios.wustl.edu> <7310001@hpscdc.HP.COM>
Reply-To: syd@dsinc.UUCP (Syd Weinstein)
Organization: Datacomp Systems, Inc., Huntingdon Valley, PA 19006
Lines: 20

In article <7310001@hpscdc.HP.COM> schmitz@hpscdc.HP.COM (John Schmitz) writes:
>Re: newmail not going away:
>Would it also be possible to record the id of the parent's shell and
>do a kill(parent_id, 0) to detect the parent shell going away?

Not all Unix's support the concept of kill(parent_id, 0) to detect
if the parent is still around.  This solution is not universal.

In fact, a program would have to be written to check, at configure
time whether this option is supported.

All we have done in 2.2, is reconnect SIGHUP if it was disconnected
by the parent.  However, this still depends on newmail being in the
same process group as the parent.  It won't solve all the problems,
but will help with some.
-- 
=====================================================================
Sydney S. Weinstein, CDP, CCP                   Elm Coordinator
Datacomp Systems, Inc.				Voice: (215) 947-9900
{allegra,bpa,vu-vlsi}!dsinc!syd	                FAX:   (215) 938-0235