On 11/14/06, Spencer Russell <slothlove@xxxxxxxxx> wrote:
On 11/14/06, Dragan Noveski <perodog@xxxxxxx> wrote: > Julian Hagenauer wrote: > > Hi, > > i am using Debian testing with libpam-modules 0.79-4. > > I added > > @audio - rtprio 99 > > @audio - nice -10 > > @audio - memlock 250000 > > to /etc/security/limits.conf and i am member of the audio-group. > I very well could be wrong, but I'm not using libpam, i'm using set_rlimits. Is one of these methods considered better/cleaner? I tried to figure out for a while how to get pam set up for rlimits, but in the end this seemed much simpler.
I think the PAM solution is better, once your distribution includes the necessary update. Trying to patch PAM yourself is probably more trouble than it's worth for most of us. With limits.conf updated and your UID added to group "audio", just log out. From then on, everything should "just work". You should not have to think about this absurd problem ever again. Sad that it has taken so many years to reach this point, and that many distributions still do not contain that fix. -- joq
