From: Frans Pop <elendil@planet.nl>
To: linux-kernel@vger.kernel.org
Cc: 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 22:48:25 +0100 [thread overview]
Message-ID: <200902262248.26713.elendil@planet.nl> (raw)
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)
Redhat's BTS [1] tells me this is a kernel issue thatshould be solved [2]
by the "rlimit: permit setting RLIMIT_NOFILE to RLIM_INFINITY" patch in
2.6.28.
One of my servers (DNS slave) is running the standard Debian 2.6.26
kernel, the other (DNS master) is running 2.6.29-rc6 so that does include
that patch. But both show the error!
I'd appreciate your input where to take this.
Cheers,
FJP
[1] https://bugzilla.redhat.com/show_bug.cgi?id=477540
[2] https://bugzilla.redhat.com/show_bug.cgi?id=461458
next reply other threads:[~2009-02-26 21:48 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-26 21:48 Frans Pop [this message]
2009-02-26 22:01 ` 2.6.28, rlimits, performance and debian etch Steve Langasek
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=200902262248.26713.elendil@planet.nl \
--to=elendil@planet.nl \
--cc=debian-admin@lists.debian.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.