This is the mail archive of the libc-help@sourceware.org mailing list for the glibc project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: clone(CLONE_VFORK) behavior

From: Mike Frysinger <vapier at gentoo dot org>
To: libc-help at sourceware dot org
Cc: David Wuertele <dave+libc-help at wuertele dot com>
Date: Tue, 30 Jun 2009 16:55:43 -0400
Subject: Re: clone(CLONE_VFORK) behavior
References: <684851e60906301202r15b51787kfb9fe68a63d0565f@mail.gmail.com>

On Tuesday 30 June 2009 15:02:41 David Wuertele wrote:
> The man page for clone() says:
>
>   If CLONE_VFORK is set, the execution of the calling process is
> suspended until the child releases its virtual memory resources via a
> call to execve(2) or _exit(2) (as with vfork(2)).

the glibc interface to clone() is merely a wrapper to the kernel.  you'll 
probably have better luck posting your question either to lkml or the man-
pages list.
-mike

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

References:
- clone(CLONE_VFORK) behavior
  - From: David Wuertele

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]