> vfork(2) [...] The child code
> between the fork() and subsequent exec() must be carefully written
> because any changes to memory (including stack) or open files will
> also be reflected in the parent.

Not open files: indeed, the main thing you typically want to do before
the exec() is opening, closing and duping files.  Stdio FILE
structures on the other hand are just like any other memory, so you
probably don't want to touch them (hence the warning in the man page
to use _exit() rather than exit()).

-- Richard

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Reply via email to