From: Rich Felker <dalias@libc.org>
To: Bruno Haible <bruno@clisp.org>
Cc: musl@lists.openwall.com, bug-gnulib@gnu.org
Subject: Re: [musl] Re: posix_spawn_file_actions_add* functions on musl libc
Date: Sun, 24 Mar 2019 17:38:01 -0400 [thread overview]
Message-ID: <20190324213801.GT23599@brightrain.aerifal.cx> (raw)
In-Reply-To: <1764808.lGQ7o5Mx7G@omega>
On Sun, Mar 24, 2019 at 07:23:16PM +0100, Bruno Haible wrote:
> Hi Rich,
>
> > -- it would preclude advance creation of a file actions object which
> > will open or dup onto high fd numbers at a later time after the rlimit
> > has been increased.
>
> This is a highly theoretical use-case, isn't it?
>
> If you think POSIX should not specify things the way it does, please
> report it to the Austin Group.
If you read the rest of my email beyond the 2.5 lines quoted above, I
said it's not clear to me that POSIX requires what you think it does
in this case. If you disagree with that, we should open a request for
interpretation.
Rich
prev parent reply other threads:[~2019-03-24 21:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-23 20:46 posix_spawn_file_actions_add* functions on musl libc Bruno Haible
2019-03-24 14:16 ` Rich Felker
2019-03-24 18:23 ` Bruno Haible
2019-03-24 21:38 ` Rich Felker [this message]
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=20190324213801.GT23599@brightrain.aerifal.cx \
--to=dalias@libc.org \
--cc=bruno@clisp.org \
--cc=bug-gnulib@gnu.org \
--cc=musl@lists.openwall.com \
/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).