Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!csd4.milw.wisc.edu!lll-winken!lll-lcc!pyramid!epimass!jbuck
From: jbuck@epimass.EPI.COM (Joe Buck)
Newsgroups: comp.mail.elm
Subject: Re: newmail also displays on console (bug)
Message-ID: <2918@epimass.EPI.COM>
Date: 1 Mar 89 21:40:06 GMT
References: <316@wubios.wustl.edu> <890001@hpausla.HP.COM> <5142@b-tech.ann-arbor.mi.us> <4774@pbhyf.PacBell.COM>
Reply-To: jbuck@epimass.EPI.COM (Joe Buck)
Organization: Entropic Processing, Inc., Cupertino, CA
Lines: 17

In article <4774@pbhyf.PacBell.COM> rob@pbhyf.PacBell.COM (Rob$Bernardo) writes:
>Newmail already obeys SIGHUP. This particular user's environment is 
>such that the SIGHUP is not being sent to newmail and that's the problem.

This particular user's environment is quite common: under the Bourne shell,
background processes don't ingnore hangup unless you use the "nohup" command,
but under the C shell they do by default.  One solution is to define
AUTO_BACKGROUND and have people run newmail without doing ampersands.
Another is to explicitly catch SIGHUP instead of keeping the default behavior,
which, as you say, depends on the environment.



-- 
-- Joe Buck	jbuck@epimass.epi.com, uunet!epimass.epi.com!jbuck

If you're not annoying somebody, you're not really alive.   - Margaret Atwood