memlock is not set
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
systemd (Debian) |
New
|
Unknown
|
|||
systemd (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
I discovered this in relation to jack, which installs /etc/security/
@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/
Also reported independently here: https:/
ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: libpam-
ProcVersionSign
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)
Changed in systemd (Debian): | |
status: | Unknown → New |
"https:/ /bugzilla. redhat. com/show_ bug.cgi? id=1364332
tl;dr it’s expected behavior since /etc/security/ limits. * is not used by systemd, and further the behavior of pam_limits with group-based limits can’t be reproduced in systemd."
https:/ /bugs.debian. org/919528# 10