Path: utzoo!attcan!uunet!lll-winken!lll-tis!helios.ee.lbl.gov!nosc!ucsd!rutgers!bellcore!tness7!tness1!sugar!ficc!peter
From: peter@ficc.uu.net (Peter da Silva)
Newsgroups: comp.unix.wizards
Subject: Re: transferring processes under csh
Keywords: job control
Message-ID: <1392@ficc.uu.net>
Date: 1 Sep 88 18:20:11 GMT
References: <1074@imagine.PAWL.RPI.EDU> <1264@mcgill-vision.UUCP> <1272@mcgill-vision.UUCP>
Organization: SCADA
Lines: 21

Way out in left feild, here...

Probably the parent should see the child as having been killed by some
new signal.

One thing that would make it easier would be to have the process that
did the attach become the child's parent. It could intercede between
the child and the shell and give the shell its return status. It takes
an extra process slot, but what the hey.

I don't think that forcing a new environment on the process is going to
be easy enough to make it worth the effort. Remember, the environment is in
the address space of the process. Anything could have happened to it. On
the PDP-11, I had one program that was tight on space trash the environment
completely.

So, tough luck on screen-based applications unless the terminal is the
same and you have a "redraw" command, or else the attach process could
move stdout to a pipe and interpret the terminal codes itself...
-- 
Peter da Silva  `-_-'  Ferranti International Controls Corporation.
"Have you hugged  U  your wolf today?"            peter@ficc.uu.net