This is the mail archive of the
libc-alpha@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 systemhalted dot org>
- To: Steven Stewart-Gallus <sstewartgallus00 at mylangara dot bc dot ca>
- Cc: "Carlos O'Donell" <carlos at redhat dot com>, "libc-help at sourceware dot org" <libc-help at sourceware dot org>, GNU C Library <libc-alpha at sourceware dot org>
- Date: Sat, 30 Aug 2014 22:15:19 -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: <fc17f0ed4ec8 dot 53ffbf5e at langara dot bc dot ca> <CAE2sS1johA-QwqCC3LmiXmjfft14qP0GYY+EpXqTDT95Vn5RkQ at mail dot gmail dot com> <fb929a1751b9 dot 5400c9ac at langara dot bc dot ca> <5400CDB0 dot 80909 at redhat dot com> <fb92ab8f358a dot 5400e09d at langara dot bc dot ca>
On Fri, Aug 29, 2014 at 4:20 PM, Steven Stewart-Gallus
<sstewartgallus00@mylangara.bc.ca> wrote:
> And I'll need to find a way to contact Google Chrome, systemd, LXC and
> Docker. I feel fine with emailing the mailing lists of systemd, LXC
> and Docker but I've had trouble getting into contact with Chrome
> developers before. Can someone else contact them for me?
Who did you reach out to at Google?
> I'll also need editor approval for my account of StevenStewartGallus
> and am CC'ing a copy of this reply to libc-alpha so I can add the wiki
> entry.
Done. You can edit the wiki now.
Cheers,
Carlos.