[Bug 1837580] Re: memlock is not set
Matthew
1837580 at bugs.launchpad.net
Wed Jul 24 09:10:32 UTC 2019
Thanks! Is something other than systemd setting the real-time priority?
Because if I move audio.conf, rtprio is no longer set:
$ulimit -l -r
max locked memory (kbytes, -l) 65536
real-time priority (-r) 0
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1837580
Title:
memlock is not set
Status in systemd package in Ubuntu:
New
Status in systemd package in Debian:
Unknown
Bug description:
I discovered this in relation to jack, which installs
/etc/security/limits.d/audio.conf, containing:
@audio - rtprio 95
@audio - memlock unlimited
For a user in the audio group:
$ulimit -l -r
max locked memory (kbytes, -l) 65536
real-time priority (-r) 95
So jack (run as user via qjackctl) reports:
ERROR: Cannot lock down 82280346 byte memory area (Cannot allocate
memory)
but does not report that it cannot set real-time priority, which it
does if run by a user not in the audio group.
I also tried putting the line in /etc/security/limits.conf, and trying
a number rather than "unlimited", but it didn't help.
Also reported independently here:
https://askubuntu.com/questions/1142943/ulimit-unlimited-cannot-set
ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: libpam-modules:amd64 1.3.1-5ubuntu1
ProcVersionSignature: Ubuntu 5.0.0-20.21-lowlatency 5.0.8
Uname: Linux 5.0.0-20-lowlatency x86_64
ApportVersion: 2.20.10-0ubuntu27.1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Jul 23 15:07:52 2019
InstallationDate: Installed on 2016-10-25 (1000 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
SourcePackage: pam
UpgradeStatus: Upgraded to disco on 2019-07-19 (3 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1837580/+subscriptions
More information about the foundations-bugs
mailing list