This is the mail archive of the
libc-help@sourceware.org
mailing list for the glibc project.
Re: What is GLibc's policy on what is safe to use after a fork from a multithreaded program?
- From: "Carlos O'Donell" <carlos at redhat dot com>
- To: Steven Stewart-Gallus <sstewartgallus00 at mylangara dot bc dot ca>
- Cc: libc-help at sourceware dot org
- Date: Wed, 03 Sep 2014 15:15:24 -0400
- Subject: Re: What is GLibc's policy on what is safe to use after a fork from a multithreaded program?
- Authentication-results: sourceware.org; auth=none
- References: <fb4bbd81a60 dot 54029393 at langara dot bc dot ca>
On 08/30/2014 11:16 PM, Steven Stewart-Gallus wrote:
> Okay I started the wiki entry (see
> https://sourceware.org/glibc/wiki/Development_Todo/Master#Improvements_to_GLibc_to_better_support_sandboxing)
> and I'll try to contact LXC, SystemD, Docker and Google Chrome.
Thank you for that!
c.