Jacek Konieczny <jajcus@xxxxxxxxxx> writes: > When using systemd to start the service, use systemd directives to set > the limits. systemd won't start PAM session for this service, so > /etc/security/limits.conf is not used. Which kind of defeats the purpose of PAM being a central configuration for all your machine's security policies, doesn't it? Isn't it nice knowing that even if you've done everything just right in /etc/pam.d, it might not matter because some parts of your system don't believe in PAM? Someday soon, if Red Hat keeps taking Linux in this direction, every config file in /etc will be like this, vestigial remains of a time when Linux machines were setup similar to other UNIX systems, now no longer used by any facility on your machine. Hail, systemd! -- - Brent Busby + =============================================== + "The introduction of a new kind of music must -- Studio -- + be shunned as imperiling the whole state, for -- Amadeus/ -- + styles of music are never disturbed without -- Keycorner -- + without affecting the most important political -- Recording -- + institutions." --Plato, "Republic" ----------------+ ===============================================
Attachment:
signature.asc
Description: PGP signature
_______________________________________________ Linux-audio-user mailing list Linux-audio-user@xxxxxxxxxxxxxxxxxxxx https://lists.linuxaudio.org/listinfo/linux-audio-user
