Re: Porting vfork()
Tim Smith (tzs@tzs.net)
Sun, 10 Jan 1999 17:12:21 -0800 (PST)
On Sun, 10 Jan 1999, Torbjorn Lindgren wrote:
> The requirements are basically (paraphrased):
> * Don't modify any data other than a variable of type pid_t used to store
> the return value from vfork()
> * Don't return from the function in which vfork() was called.
> * Don't call any functions before successfully calling _exit(),or one of
> the exec family of functions.
That last requirement seems overly stringent. I'd expect the child to be
able to (and need to) call open, close, dup, fcntl, etc., to deal with
IO redirection before calling exec.
--Tim Smith
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/