Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!emory!ogicse!mintaka!snorkelwacker.mit.edu!thunder.mcrcim.mcgill.edu!mouse
From: mouse@thunder.mcrcim.mcgill.edu (der Mouse)
Newsgroups: comp.unix.questions
Subject: Re: vfork()
Keywords: vfork()
Message-ID: <1991Mar26.122250.10343@thunder.mcrcim.mcgill.edu>
Date: 26 Mar 91 12:22:50 GMT
References: <8372@rsiatl.Dixie.Com> <15533@smoke.brl.mil> <7449@idunno.Princeton.EDU>
Organization: McGill Research Centre for Intelligent Machines
Lines: 16

In article <7449@idunno.Princeton.EDU>, pfalstad@phoenix.Princeton.EDU (Paul Falstad) writes:
> [various stuff about vfork()]

> You could even use this call for a horribly unportable shared memory
> hack if you wanted.

I did, once.  The child signaled failure to exec() by setting a
variable before exiting.

I think the program has by now died the death it deserved, thankfully.

					der Mouse

			old: mcgill-vision!mouse
			new: mouse@larry.mcrcim.mcgill.edu