Path: utzoo!attcan!uunet!cs.utexas.edu!csd4.csd.uwm.edu!mailrus!cwjcc!hal!ncoast!allbery
From: allbery@NCoast.ORG (Brandon S. Allbery)
Newsgroups: comp.unix.wizards
Subject: Re: killing bkgnd process on logout (was: Re^2: Checking for new mail)
Message-ID: <1989Sep3.124134.25376@NCoast.ORG>
Date: 3 Sep 89 12:41:34 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: allbery@ncoast.UUCP (Brandon S. Allbery)
Followup-To: comp.unix.wizards
Organization: North Coast Public Access UN*X, Cleveland, OH
Lines: 25

As quoted from <130@isgtec.UUCP> by bmw@isgtec.UUCP (Bruce Walker):
+---------------
| 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.
| 
| 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.
+---------------

Sorry, it's a BSD-vs.-Sys5 issue.  csh doesn't act the same under System V
because System V doesn't handle process groups the same way BSD does.  BSD
process groups are used to implement job control; this is why a backgrounded
process in a job-control environment (like csh) detaches from the terminal.

++Brandon
-- 
Brandon S. Allbery, moderator of comp.sources.misc	     allbery@NCoast.ORG
uunet!hal.cwru.edu!ncoast!allbery		    ncoast!allbery@hal.cwru.edu
"Why do trans-atlantic transfers take so long?"
"Electrons don't swim very fast."  -john@minster.york.ac.uk and whh@PacBell.COM