From: Florian Weimer <fw@deneb.enyo.de>
To: linux-kernel@vger.kernel.org
Cc: DSA <debian-admin@lists.debian.org>,
team@security.debian.org, libpam-modules@packages.debian.org
Subject: Re: 2.6.28, rlimits, performance and debian etch
Date: Fri, 23 Jan 2009 22:07:27 +0100 [thread overview]
Message-ID: <8763k5u3xs.fsf@mid.deneb.enyo.de> (raw)
In-Reply-To: <20090121115219.GA2754@anguilla.noreply.org> (Peter Palfrader's message of "Wed, 21 Jan 2009 12:52:19 +0100")
* Peter Palfrader:
> Turns out that script is forking a lot and something in it or python or
> whereever closes all the file descriptors it doesn't want to pass on.
> That is, it starts at zero and goes up to ulimit -n/RLIMIT_NOFILE and
> closes them all with a few exceptions.
>
> Turns out that takes a long time when your limit -n is now 2^20 (1048576).
Interesting.
Can we make /proc more-or-less mandatory, so that the file descriptor
list can be retrieved explicitly?
next prev parent reply other threads:[~2009-01-23 21:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-21 11:52 2.6.28, rlimits, performance and debian etch Peter Palfrader
2009-01-23 21:07 ` Florian Weimer [this message]
2009-01-23 22:02 ` David Daney
2009-01-23 23:11 ` Peter Palfrader
2009-01-25 10:59 ` Florian Weimer
2009-01-27 23:17 ` Andrew Morton
2009-01-29 12:19 ` Adam Tkac
2009-01-29 18:05 ` Andrew Morton
2009-01-29 18:10 ` Peter Palfrader
2009-02-02 16:20 ` Adam Tkac
2009-02-08 22:31 ` Steve Langasek
-- strict thread matches above, loose matches on Subject: below --
2009-02-26 21:48 Frans Pop
2009-02-26 22:01 ` Steve Langasek
2009-02-27 7:30 ` Peter Palfrader
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=8763k5u3xs.fsf@mid.deneb.enyo.de \
--to=fw@deneb.enyo.de \
--cc=debian-admin@lists.debian.org \
--cc=libpam-modules@packages.debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=team@security.debian.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