This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: O_CLOEXEC and SOCK_CLOEXEC
- From: Florian Weimer <fweimer at redhat dot com>
- To: Roland McGrath <roland at hack dot frob dot com>
- Cc: GNU C Library <libc-alpha at sourceware dot org>
- Date: Thu, 8 Oct 2015 08:20:11 +0200
- Subject: Re: O_CLOEXEC and SOCK_CLOEXEC
- Authentication-results: sourceware.org; auth=none
- References: <56152F14 dot 5050606 at redhat dot com> <20151007200432 dot B6B732C39DF at topped-with-meat dot com>
On 10/07/2015 10:04 PM, Roland McGrath wrote:
> NaCl defines them but doesn't actually support them.
> But it doesn't actually support FD_CLOEXEC either.
> So you can consider NaCl to "support" O_CLOEXEC.
>
> On the Hurd, these are implemented entirely in libc. So if any part of the
> support is missing, it can be fixed in libc.
What about SOCK_NONBLOCK? There is fallback code which looks at the
SOCK_CLOEXEC flag, but actually uses SOCK_NONBLOCK.