From: Paul Eggert <eggert@cs.ucla.edu>
To: Bruno Haible <bruno@clisp.org>
Cc: bug-gnulib@gnu.org
Subject: Re: use O_CLOEXEC in more places
Date: Wed, 27 May 2020 16:33:06 -0700 [thread overview]
Message-ID: <3fb846cc-a709-b6bb-5615-20482bb98950@cs.ucla.edu> (raw)
In-Reply-To: <2127200.Gmmp1eMdPG@omega>
On 5/27/20 11:43 AM, Bruno Haible wrote:
> How about module 'fts'? Should the directory fds that it allocates also be
> made O_CLOEXEC?
Yes, I'd say so; I see little reason for a child process to continue an fts scan.
next prev parent reply other threads:[~2020-05-27 23:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-27 18:43 use O_CLOEXEC in more places Bruno Haible
2020-05-27 21:55 ` Bernhard Voelker
2020-05-27 22:21 ` Jim Meyering
2020-05-27 23:33 ` Paul Eggert [this message]
2020-05-28 19:51 ` Bruno Haible
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.gnu.org/mailman/listinfo/bug-gnulib
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3fb846cc-a709-b6bb-5615-20482bb98950@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=bruno@clisp.org \
--cc=bug-gnulib@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).