[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#596382: kfreebsd-image-8.1-1-686: "kern.proc.all" sysctl returns nothing/error. (SOLVED?)

On Sun, Nov 07, 2010 at 07:16:22PM +0100, Petr Salinger wrote:
> >This happens since RLIMIT_MEMLOCK is 65536 but you are trying to lock
> >170496 bytes. If I remove the limit for locked memory everything seems
> >to work:

> ># ulimit -l
> ># sysctl -x kern.proc.all
> >kern.proc.all: Format:S,proc Length:79104 Dump:0x0003000000000000804459...

> >Can you please confirm that this works for you too?

> For me too.

> It looks like the problem comes from pam:
> the debian patch 027_pam_limits_better_init_allow_explicit_root
> in order to fix #472629..

> It would be better to not change (or not lower) RLIMIT_MEMLOCK
> by default on non-linux :-(

Please open a bug report against the libpam-modules package for this.

The intent of this patch is to always reset the limits to the kernel
defaults; unfortunately up to now this has been implemented by including the
current known defaults at compile time.  We should actually be picking these
up at runtime by querying the kernel; on Linux this will be by parsing
/proc/1/limits, on other kernels I'll be dependent on porters to let me know
where we can query this info.  (I doubt 'sysctl -x' is the interface we want
to use from inside pam_limits, and anyway, I have no idea how to parse the
line you quoted above.)

If someone were to provide a preliminary patch implementing this, that would
be most welcome.

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

Attachment: signature.asc
Description: Digital signature

Reply to: