[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [] Adding code for fork/vfork?

From: Mike Frysinger
Subject: Re: [] Adding code for fork/vfork?
Date: Fri, 15 Apr 2011 19:02:01 -0400
User-agent: KMail/1.13.6 (Linux/; KDE/4.6.0; x86_64; ; )

On Friday, April 15, 2011 18:53:24 Bob Friesenhahn wrote:
> On Fri, 15 Apr 2011, Mike Frysinger wrote:
> >> If you do not want to "force" people to change their code, you will
> >> probably need to offer a "stub" fork() to link against on non-MMU CPUs.
> > 
> > the majority of the time, it isnt just fork() that needs to change.  any
> > exit() in the child needs to be changed to _exit() too.
> The sole purpose of vfork is to immediately invoke exec()  Any other
> purpose is forbidden.  In what case would an exit even be required?

ignoring the fact that Linux allows many many more things to safely happen in 
the child of a vfork, what exactly are you supposed to do when that exec fails 
and returns ?  or you pray it never does ?

Attachment: signature.asc
Description: This is a digitally signed message part.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]