Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!ucsd!ucbvax!agate!darkstar!kithrup!sef
From: sef@kithrup.COM (Sean Eric Fagan)
Newsgroups: comp.unix.questions
Subject: Re: vfork()
Keywords: vfork()
Message-ID: <1991Mar27.211804.17712@kithrup.COM>
Date: 27 Mar 91 21:18:04 GMT
References: <15533@smoke.brl.mil> <1135@pemcom.pem-stuttgart.de> <6834@auspex.auspex.com>
Organization: Kithrup Enterprises, Ltd.
Lines: 16

In article <6834@auspex.auspex.com> guy@auspex.auspex.com (Guy Harris) writes:
>That's precisely what Doug was referring to; either the application
>*doesn't* depend on the fact that, in most if not all current
>implementations, "vfork()" causes the parent and child to temporarily
>share an address space, in which case the original poster can just
>replace the "vfork()" calls with "fork()"

Of course, it (the application) may also depend on the fact that the child
is guaranteed to execute *before* the parent (which is an extremely useful
thing, I will admit), in which case you cannot replace it with a fork().

-- 
Sean Eric Fagan  | "I made the universe, but please don't blame me for it;
sef@kithrup.COM  |  I had a bellyache at the time."
-----------------+           -- The Turtle (Stephen King, _It_)
Any opinions expressed are my own, and generally unpopular with others.