Re: [PATCH] Realtime LSM

[Jack O'Quin]

Chris Wright <chrisw@xxxxxxxx> writes:

> This uses the basic rlimits infrastructure.  You can manage it manually
> in a shell with ulimit -l, or you can use pam (pam_limits) to configure
> per uid limits.  There's a pam doc that describes limits, and a manpage
> for ulimit.  It's really easy to use, and should eliminate the need for
> the mlock part of that module.

Thanks for the pointer, Chris.

I'll see if I can figure out a way to make that useable for musicians.

The ulimit approach is way too cumbersome.

The pam_limits solution is not well-documented on my Debian system,
which doesn't even have a man page for /etc/security/limits.conf,
though the file has comments, now that I know where to look.  PAM is
powerful and flexible, but "easy to use" is not a phrase that comes
readily to mind.  :-)

The PAM approach would probably be workable for special-purpose audio
distributions like Planet CCRMA or DeMuDi.  That still leaves all the
audio developers with a significant challenge trying to explain every
configuration step to all our other users.  AFAICT, PAM configuration
is rather distribution-specific, so that could become a significant
burden.

It appears that a limits.conf line like this might work...

@audio - memlock 10000        # is there any way to say "unlimited"?

I'll experiment tomorrow to see if I can actually make this work.
-- 
  joq
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/