Re: [LAU] memlock limits not set correctly?

From: Bill Gribble <grib@email-addr-hidden>
Date: Thu Jan 17 2019 - 00:12:59 EET

On 1/16/19 5:02 PM, Michael Jarosch wrote:
> I also tried this on my laptop, a debian testing system:
> :~$ ulimit
> unlimited
>
> :~$ ulimit -l
> 65536
>
> Can someone explain the difference?
> /etc/security/limits.d/audio.conf says:
>
> @audio - rtprio 95
> @audio - memlock unlimited

Thanks for this.  I too am on a Debian system, so this is probably a
Debian-specific problem.

"ulimit" with no arguments prints the maximum file size limit, and is a
synonym for "ulimit -f".

To see all user limits, "ulimit -a".  "ulimit -l" just prints the
maximum size of a memory locked segment in MB.

The behavior you are seeing is the same as mine: the limit setting in
/etc/security/limits.d/audio.conf is not being respected (assuming that
the user from which you printed that transcript is in the "audio" group).

I have opened a Debian bug report against the "libpam-modules" package
(containing pam_limits.so, the module that actually reads and applies
the /etc/security/limits.{conf,d} limits).  We'll see what happens!

bg
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user@lists.linuxaudio.org
https://lists.linuxaudio.org/listinfo/linux-audio-user
Received on Thu Jan 17 00:15:02 2019

This archive was generated by hypermail 2.1.8 : Thu Jan 17 2019 - 00:15:02 EET