Source: pam Version: 1.1.8-3.8 Severity: important Dear Maintainer,
The SystemD 240 update has changed the handling of NOFILE for the init process and processes it directly spawns. See: https://github.com/systemd/systemd/pull/10244 Unfortunately, it seems that the patch above, which is forcing NOFILE to "infinity" (effectively 1G?) is now having a serious adverse effect on various processes that are spawned by SystemD directly, see: https://github.com/systemd/systemd/issues/10921 and a KDE init bug similarly. I can't find a bug reporting this to debian, even though the root cause seems to be this patch to force "infinity" onto PID 1. Hope this helps. -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'stable'), (499, 'testing'), (399, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-1-amd64 (SMP w/8 CPU cores) Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), LANGUAGE=en_CA.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
