From: Steve Langasek <vorlon@debian.org>
To: Frans Pop <elendil@planet.nl>
Cc: linux-kernel@vger.kernel.org, libpam-modules@packages.debian.org,
debian-admin@lists.debian.org
Subject: Re: 2.6.28, rlimits, performance and debian etch
Date: Thu, 26 Feb 2009 14:01:36 -0800 [thread overview]
Message-ID: <20090226220136.GA24667@dario.dodds.net> (raw)
In-Reply-To: <200902262248.26713.elendil@planet.nl>
On Thu, Feb 26, 2009 at 10:48:25PM +0100, Frans Pop wrote:
> Steve Langasek wrote:
> > It has already been mentioned that this does not apply to the upcoming
> > Debian 5.0 release (lenny); this patch is only present in the 4.0
> > release (etch), it was actually fixed in the development series to not
> > use RLIM_INFINITY *because* previous kernels didn't support this and
> > would cause pam_limits to throw log warnings.
> I've just migrated my home servers from Debian etch to lenny and bind9 now
> gives me this:
> named[17207]: max open files (1024) is smaller than max sockets (4096)
That's a separate issue; Debian bug #515673. I intend to solve this for
Debian 5.0.1.
--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
Ubuntu Developer http://www.debian.org/
slangasek@ubuntu.com vorlon@debian.org
next prev parent reply other threads:[~2009-02-26 22:01 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-26 21:48 2.6.28, rlimits, performance and debian etch Frans Pop
2009-02-26 22:01 ` Steve Langasek [this message]
2009-02-27 7:30 ` Peter Palfrader
-- strict thread matches above, loose matches on Subject: below --
2009-01-21 11:52 Peter Palfrader
2009-01-23 21:07 ` Florian Weimer
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
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=20090226220136.GA24667@dario.dodds.net \
--to=vorlon@debian.org \
--cc=debian-admin@lists.debian.org \
--cc=elendil@planet.nl \
--cc=libpam-modules@packages.debian.org \
--cc=linux-kernel@vger.kernel.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