Your message dated Mon, 20 Jan 2025 12:13:17 -0700
with message-id <[email protected]>
and subject line Not a bug?
has caused the Debian Bug report #919528,
regarding libpam-modules: pam_limits.so does not appear to read
/etc/security/limits.{conf,d}
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
919528: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919528
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: libpam-modules
Version: 1.1.8-4
Severity: normal
Dear Maintainer,
I use my Debian system for music production and so depend on
various real-time features, including memory locking.
Recently a program that I use (aeolus) started failing on launch
when it could not lock the required shm segment. The shm segment,
as it turns out, is about 85 MB. I'm not sure exactly when this behavior
started; the last time I (successfully) attempted to use Aeolus was
probably 3-4 months ago, and I first noticed the failure on 2019-01-12
on an up-to-date unstable system.
For some time I have had this line in /etc/security/limits.d/audio.conf:
@audio - memlock unlimited
My main user account is in the audio group:
grib@ghost:~$ groups
grib cdrom floppy audio dip video plugdev staff netdev bluetooth
Yet the memlock limit is not set as requested:
grib@ghost:~$ ulimit -l
65536
I have attempted to set the "memlock" limit in /etc/security/limits.conf
directly, to apply it to my user account specifically, to apply
it to all users. Nothing works. The limit is always the same.
To test the setting of limits in general, I performed some experiments
with setting the limit on core size with the same results: regardless
of the contents of /etc/security/limits.conf or /etc/security/limits.d/*
the maximum core dump size is always 0.
I have not modified the files in /etc/pam.d and the relevant ones all
include pam_limits.so:
grib@ghost:/etc/pam.d$ ack pam_limits
gdm-autologin
18:session required pam_limits.so
systemd-user
10:session required pam_limits.so
common-session
28:session required pam_limits.so
gdm-password
17:session required pam_limits.so
gdm-launch-environment
6:session required pam_limits.so
login
87:session required pam_limits.so
sshd
40:session required pam_limits.so
cron
20:session required pam_limits.so
runuser
4:session required pam_limits.so
su
52:session required pam_limits.so
gdm-fingerprint
17:session required pam_limits.so
-- System Information:
Debian Release: buster/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.19.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages libpam-modules depends on:
ii debconf [debconf-2.0] 1.5.70
ii libaudit1 1:2.8.4-2
ii libc6 2.28-5
ii libdb5.3 5.3.28+dfsg1-0.2
ii libpam-modules-bin 1.1.8-4
ii libpam0g 1.1.8-4
ii libselinux1 2.8-1+b1
libpam-modules recommends no packages.
libpam-modules suggests no packages.
-- Configuration Files:
/etc/security/limits.conf changed [not included]
-- debconf information:
libpam-modules/disable-screensaver:
--- End Message ---
--- Begin Message ---
I'm confused.
This does not appear to be a pam issue, but rather a systemd issue.
--- End Message ---
