On Mo, 20.11.17 08:32, Jeff Solomon (jsolomon8...@gmail.com) wrote: > I am using lingering and I have issued "systemctl restart user@<uid>" and > then seen the instance restart with a new PID. So I think I am restarting > the user instance. > > When Limit* directives are applied in "user@.service" or in > "/etc/systemd/system/user@.service.d/whatever.conf" I see that they are > respected in the user instance itself and the child processes it starts. > > However, I do NOT see settings applied through pam_limits > (/etc/security/limits.d etc etc) respected in the user instance although > Mantas implied that I should. Is this expected?
When systemd executes a service that has PAM enabled, it will will first start the PAM session, which is where pam_limits does its thing. It then goes on setting up the execution environment for the service, and if resource limits are configured for the unit, they'll be put into effect. This means that any settings configured in the unit file they take precedence over the pam_limits settings. Lennart -- Lennart Poettering, Red Hat _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
