This is the mail archive of the
libc-help@sourceware.org
mailing list for the glibc project.
Re: static fork strerror and how they interact.
- From: "Carlos O'Donell" <carlos at systemhalted dot org>
- To: Ãngel GonzÃlez <keisial at gmail dot com>
- Cc: "libc-help at sourceware dot org" <libc-help at sourceware dot org>
- Date: Mon, 21 Dec 2015 10:12:01 -0500
- Subject: Re: static fork strerror and how they interact.
- Authentication-results: sourceware.org; auth=none
- References: <trinity-e1774b10-9cc4-4e09-8dce-005525e3c848-1414501291095 at 3capp-mailcom-lxa08> <CAE2sS1iVCRNNneppQEU1C+4OXWV7g9FqRuYKweNFJpRTQW8BEw at mail dot gmail dot com> <56773521 dot 1040509 at gmail dot com>
On Sun, Dec 20, 2015 at 6:09 PM, Ãngel GonzÃlez <keisial@gmail.com> wrote:
> On 28/10/14 15:02, Carlos O'Donell wrote:
>>
>> Even more complicated is using vfork safely from a multi-threaded
>> application. I have written up a very thorough example on this, but
>> have not posted it yet.
>
> Did you finally publish this?
Yes.
You can read it here:
http://developerblog.redhat.com/2015/08/19/launching-helper-process-under-memory-and-latency-constraints-pthread_create-and-vfork/
Cheers,
Carlos.