qfork() (again)
Sean Eric Fagan
sef at kithrup.COM
Sun Feb 3 16:30:06 AEST 1991
Submitted-by: sef at kithrup.COM (Sean Eric Fagan)
In article <17572 at cs.utexas.edu> eggert at twinsun.uucp (Paul Eggert) writes:
>What's wrong with the following definition, which permits the usual actions
>between fork() and exec()? Isn't this definition easy to explain and support?
[stuff]
Because one of the few reasons I would like vfork() (or something similar)
is now missing: the parent does not execute until the child has exit'ed or
exec'ed something.
--
Sean Eric Fagan | "I made the universe, but please don't blame me for it;
sef at 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.
Volume-Number: Volume 22, Number 99
More information about the Comp.std.unix
mailing list