Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!hellgate.utah.edu!cs.utexas.edu!uunet!mcsun!sunic!dkuug!harald.ruc.dk!jba
From: jba@harald.ruc.dk (Jan B. Andersen)
Newsgroups: comp.unix.wizards
Subject: Re: killing bkgnd process on logout (was: Re^2: Checking for new mail)
Message-ID: <93@harald.UUCP>
Date: 1 Sep 89 11:11:48 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>
Organization: RUC - Roskilde University Center, Denmark
Lines: 27

bmw@isgtec.UUCP (Bruce Walker) writes:

-In article <92@harald.UUCP> jba@harald.ruc.dk (Jan B. Andersen) writes:
->>In article <128@isgtec.UUCP> bmw@isgtec.UUCP (Bruce Walker) writes:
->>[ in BSD systems ]
->>the process disconnects from your tty and continues running ...
->
->This has nothing to do with BSD vs Sys V.
->
->        [CSH man page excerpt deleted]

-Well, it sort-of does.  Csh's under SysV are usually sub-sets of full-blown
-BSD csh's, and don't behave the same.

-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.

The man page I quoted was from a NCR Tower running some sort of System V
(it definitly isn't BSD). Although I would prefer it to behave like the
sh(1) I would much more prefer _every_ csh(1) to behave exactly the same.
And that means behave like a genuie BSD csh.

-Bruce Walker                          ...uunet!mnetor!lsuc!isgtec!bmw

Sorry for all this quoting, but I found it nescessary.