Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!csd4.csd.uwm.edu!gem.mps.ohio-state.edu!ginosko!usc!polyslo!cindy!csusac!unify!jwc
From: jwc@unify.UUCP (J. William )
Newsgroups: comp.unix.wizards
Subject: Re: killing bkgnd process on logout (was: Re^2: Checking for new mail)
Message-ID: <1091@unify.UUCP>
Date: 2 Sep 89 15:34:22 GMT
References: <105@csnz.co.nz> <1989Aug26.200813.15629@twwells.com> <64@calcite.UUCP> <128@isgtec.UUCP> <1989Aug30.053137.2047@ctr.columbia.edu> <92@harald.UUCP> <130@isgtec.UUCP>
Reply-To: jwc@unify.UUCP (J. William (Bill) Claypool)
Organization: Unify Corporation, Sacramento, CA, USA
Lines: 16

In article <130@isgtec.UUCP> bmw@isgtec.UUCP (Bruce Walker) writes:
> [...]
>If I run my checkmail process in the background from CTIX csh, then log out,
>checkmail dies.  If I do that on Sun csh, it behaves as your man page
>suggests (ignores SIGHUP).  I suspect that other SysV csh's also behave more
>like sh(1) than BSD csh in this regard.

I suspect that when checkmail is not ignoring SIGHUP.  Rather, BSD csh
puts each background job into a separate process group to facilitate
job control.  Only the process group currently in the forground is
attached to the controlling terminal.
-- 

Bill Claypool    W. (916) 920-9092 | I know what I know if you know what I mean
jwc@unify.UUCP   H. (916) 381-4205 |-------------------------------------------
    ...!{csusac,pyramid}!unify!jwc |      SCCA SFR Solo II 74 es '84 CRX