qfork()
Paul Eggert
eggert at twinsun.uucp
Thu Dec 27 08:22:33 AEST 1990
Submitted-by: eggert at twinsun.uucp (Paul Eggert)
jason at cnd.hp.com (Jason Zions) writes:
The intent of the [Posix.1a draft 5] text, I believe, is that *doing* anything
between qfork() and exec*() [or _exit()] results in undefined behavior.
I hope this is not the intent. Current applications often do the following
actions between forking and execing in a child process:
Redirect file descriptors using open(), close(), dup2().
Call write() and _exit() if the exec*() fails.
Change signal handling, uid/gid/pgid/session, working/root directory.
Call user-defined functions that modify their local variables.
Both fork() and vfork() permit these actions. Why should qfork() prohibit them?
Volume-Number: Volume 22, Number 42
More information about the Comp.std.unix
mailing list