public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "roland at gnu dot org" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sources.redhat.com Subject: [Bug libc/1535] Make _SC_CHILD_MAX retort RLIMIT_NPROC soft resource limit? Date: Sun, 08 Jan 2006 09:44:00 -0000 [thread overview] Message-ID: <20060108094406.5178.qmail@sourceware.org> (raw) In-Reply-To: <20051024142054.1535.michael.kerrisk@gmx.net> ------- Additional Comments From roland at gnu dot org 2006-01-08 09:44 ------- I've committed code on the trunk that will use the RLIMIT_NPROC value in sysconf when CHILD_MAX is not defined at compile time. This has no effect until the kernel header is changed to remove CHILD_MAX, and then a glibc compiled against thew new kernel headers will yield the dynamic value, matching applications compiled against those headers that expect a runtime-variable value. Because CHILD_MAX is specified as a runtime invariant value, we are not at liberty to make sysconf return a different value from the CHILD_MAX constant as long as one is defined. This requirement will be violated when there is skew between built applications using an old CHILD_MAX value from old kernel headers, and a newer libc.so built against new kernel headers. But that is the same violation that occurs whenever libc.so is built against new kernel headers that have changed the constant value, just the same as removing the constant. -- http://sourceware.org/bugzilla/show_bug.cgi?id=1535 ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
prev parent reply other threads:[~2006-01-08 9:44 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-10-24 14:21 [Bug libc/1535] New: " michael dot kerrisk at gmx dot net 2005-12-23 6:11 ` [Bug libc/1535] " drepper at redhat dot com 2006-01-08 9:39 ` cvs-commit at gcc dot gnu dot org 2006-01-08 9:44 ` roland at gnu dot org [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 * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20060108094406.5178.qmail@sourceware.org \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@sources.redhat.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: linkBe 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).