[Bug 1837580] Re: memlock is not set

2021-07-01 Thread Dan Streetman
please reopen if this is still an issue ** Changed in: systemd (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1837580 Title: memlock is not set To

[Bug 1837580] Re: memlock is not set

2020-03-29 Thread tomy
try this : modif : /etc/systemd/user.conf /etc/systemd/system.conf with : DefaultlimitNOFILE=65535 DefaultlimitMEMLOCK=500 modif : /etc/security/limits.conf with : mkasberg hard nofile 65535 mkasberg soft nofile 65535 @sudo hard

[Bug 1837580] Re: memlock is not set

2019-11-22 Thread Jeff Dileo
This is currently an issue in 19.10's systemd (version 242). By default, unless services are configured to set LimitMEMLOCK, they will have 64k as their memlock limit (though oddly, systemd bumped its own memlock limit higher than previous versions have used). The only processes not affected are

[Bug 1837580] Re: memlock is not set

2019-11-22 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: systemd (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1837580 Title:

[Bug 1837580] Re: memlock is not set

2019-09-02 Thread Bug Watch Updater
** Changed in: systemd (Debian) Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1837580 Title: memlock is not set To manage notifications about this bug go to:

[Bug 1837580] Re: memlock is not set

2019-08-16 Thread Kain
Actually, its just systemd 240. Looks fixed in 241 and newer. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1837580 Title: memlock is not set To manage notifications about this bug go to:

[Bug 1837580] Re: memlock is not set

2019-08-16 Thread Kain
Systemd 240 and newer introduced a clamp to RLIMIT_MEMLOCK in c8884aceefc85245b9bdfb626e2daf27521259bd. See https://github.com/systemd/systemd/issues/13331. ** Bug watch added: github.com/systemd/systemd/issues #13331 https://github.com/systemd/systemd/issues/13331 -- You received this bug

[Bug 1837580] Re: memlock is not set

2019-08-13 Thread Mauro Panigada
The same happens to me, same distro, some infos are different (namely the kernel, 4.18.0-18-generic, since 5.0.0... frozes my machine - another issue to be investigated), but I don't think these differences are relevant. I've set DefaultLimitMEMLOCK=infinity in /etc/systemd/system.conf and also

[Bug 1837580] Re: memlock is not set

2019-07-24 Thread Matthew
I can REDUCE the memlock limit in /etc/systemd/system.conf, or by creating /etc/systemd/system.conf.d/ and a file in that, but cannot increase it beyond 65536kB. For instance: [Manager] DefaultLimitMEMLOCK=100M does nothing, and neither does specifying "infinity". -- You received this bug

[Bug 1837580] Re: memlock is not set

2019-07-24 Thread Matthew
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

[Bug 1837580] Re: memlock is not set

2019-07-23 Thread Steve Langasek
"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 ** Bug watch added: Red Hat

[Bug 1837580] Re: memlock is not set

2019-07-23 Thread Steve Langasek
systemd user fighting PAM for limits is from my POV certainly a systemd bug. ** Package changed: pam (Ubuntu) => systemd (Ubuntu) ** Also affects: systemd (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919528 Importance: Unknown Status: Unknown -- You received this