mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Rich Felker <dalias@libc.org>
To: Tavian Barnes <tavianator@tavianator.com>
Cc: musl@lists.openwall.com
Subject: Re: [musl] Feature request: posix_spawnattr_setrlimit_np()
Date: Wed, 15 Nov 2023 17:39:03 -0500	[thread overview]
Message-ID: <20231115223902.GY4163@brightrain.aerifal.cx> (raw)
In-Reply-To: <CABg4E-k1G6zZkYj_d7hNxnREQC+S3Wr7KfRmYCTng0w3SQKcBQ@mail.gmail.com>

On Wed, Nov 15, 2023 at 05:00:51PM -0500, Tavian Barnes wrote:
> I have a program that raises its soft RLIMIT_NOFILE, but wants to
> spawn processes with the original value (in case they use select(),
> for example).  There seems to be no nice way to do this with
> posix_spawn().  I can temporarily lower the rlimit in the parent, but
> that interferes with other threads, and can make posix_spawn() fail
> with EMFILE.
> 
> Corresponding glibc feature request:
> https://sourceware.org/bugzilla/show_bug.cgi?id=31049

I don't have any objection to this as long as it's coordinated and
there's agreement from other implementors, but there *is* a way to do
it already. You posix_spawnp:

sh -c 'ulimit -n whatever && exec "$0" "$@"' your_program args...

This is the general solution to doing all sorts of "child process
state setup" things that posix_spawn doesn't have a dedicated
attribute for.

Note that for a proposal for setting rlimits via an attribute, one
complication that needs to be specified is whether the limits take
place before or after file actions, since they could change the
outcome of file actions. I'm not sure what the answer is, but just
YOLO'ing an implementation without thinking about that is a bad idea.

Rich

  reply	other threads:[~2023-11-15 22:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-15 22:00 Tavian Barnes
2023-11-15 22:39 ` Rich Felker [this message]
2023-11-16  0:29   ` Tavian Barnes
2023-11-16 16:23     ` Adhemerval Zanella Netto

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20231115223902.GY4163@brightrain.aerifal.cx \
    --to=dalias@libc.org \
    --cc=musl@lists.openwall.com \
    --cc=tavianator@tavianator.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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/musl/

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 NNTP newsgroup(s).