Hi!

I wonder how

pam (1.7.0-1) unstable; urgency=medium

    Starting with pam 1.7.0, pam_limits does not automatically reset the
    limits of logged in users. This means that systemd, rather than pam will
    set the defaults for things like number of open files and other resource
    limits. If limits are configured in /etc/security/limits.conf or
    /etc/security/limits.d/*.conf, these values will be respected. To
    restore the previous behavior, add the set_all option to pam_limits.
    For example in /etc/pam.d/ssh, replace:

    session    required     pam_limits.so

    with:

    session    required     pam_limits.so set_all

-- Sam Hartman <[…]> Tue, 14 Jan 2025 15:47:56 -0700

affects users that use an other than Systemd' init.

Any idea?

A gut feeling tells me that I do not like this change. Would Systemd
prepare my tea by end of 2025 if I would use it? How about stuffing
an AI into Systemd? On one hand I do not like to give them any
additional crazy idea… however does it even really matter anymore?

Systemd is a pile of doing-everything-and-then-some-stuffed-all-into-one
software. I cannot even identify a clear shape of this software anymore.

Best,
--
Martin