bug-gnulib@gnu.org mirror (unofficial)
 help / color / mirror / Atom feed
From: Bruno Haible <bruno@clisp.org>
To: Rich Felker <dalias@libc.org>
Cc: musl@lists.openwall.com, bug-gnulib@gnu.org
Subject: Re: posix_spawn_file_actions_add* functions on musl libc
Date: Sun, 24 Mar 2019 19:23:16 +0100	[thread overview]
Message-ID: <1764808.lGQ7o5Mx7G@omega> (raw)
In-Reply-To: <20190324141658.GR23599@brightrain.aerifal.cx>

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.

Bruno



  reply	other threads:[~2019-03-24 18:23 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 [this message]
2019-03-24 21:38     ` [musl] " Rich Felker

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=1764808.lGQ7o5Mx7G@omega \
    --to=bruno@clisp.org \
    --cc=bug-gnulib@gnu.org \
    --cc=dalias@libc.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).