public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "tavianator at tavianator dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug libc/31049] New: Feature request: posix_spawnattr_setrlimit_np()
Date: Thu, 09 Nov 2023 21:51:46 +0000	[thread overview]
Message-ID: <bug-31049-131@http.sourceware.org/bugzilla/> (raw)

https://sourceware.org/bugzilla/show_bug.cgi?id=31049

            Bug ID: 31049
           Summary: Feature request: posix_spawnattr_setrlimit_np()
           Product: glibc
           Version: unspecified
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: libc
          Assignee: unassigned at sourceware dot org
          Reporter: tavianator at tavianator dot com
                CC: drepper.fsp at gmail dot com
  Target Milestone: ---

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.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

             reply	other threads:[~2023-11-09 21:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-09 21:51 tavianator at tavianator dot com [this message]
2023-11-14 20:55 ` [Bug libc/31049] " adhemerval.zanella at linaro dot org
2023-11-14 21:03 ` tavianator at tavianator dot com
2023-11-15 12:52 ` adhemerval.zanella at linaro dot org
2023-11-15 13:12 ` adhemerval.zanella at linaro dot org
2023-11-15 13:49 ` tavianator at tavianator dot com

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=bug-31049-131@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@sourceware.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).