Re: [systemd-devel] systemd user instance and raising limits

2017-11-20 Thread Jeff Solomon
Good to know! Thanks for googling for me! On Mon, Nov 20, 2017 at 10:29 AM, Michael Biebl wrote: > 2017-11-20 19:26 GMT+01:00 Michael Biebl : > > https://anonscm.debian.org/git/pkg-systemd/systemd.git/ > commit/debian/extra/pam.d/systemd-user?id=b3238e9604fa61c7ec45a2d0acc1f8 > b40728cd87 > > >

Re: [systemd-devel] systemd user instance and raising limits

2017-11-20 Thread Michael Biebl
2017-11-20 19:26 GMT+01:00 Michael Biebl : > https://anonscm.debian.org/git/pkg-systemd/systemd.git/commit/debian/extra/pam.d/systemd-user?id=b3238e9604fa61c7ec45a2d0acc1f8b40728cd87 > > This might be relevant to you. > > See how the pam config contains pam_limits This was a result of https://bugs

Re: [systemd-devel] systemd user instance and raising limits

2017-11-20 Thread Michael Biebl
https://anonscm.debian.org/git/pkg-systemd/systemd.git/commit/debian/extra/pam.d/systemd-user?id=b3238e9604fa61c7ec45a2d0acc1f8b40728cd87 This might be relevant to you. See how the pam config contains pam_limits 2017-11-20 18:49 GMT+01:00 Lennart Poettering : > On Mo, 20.11.17 09:47, Jeff Solomo

Re: [systemd-devel] systemd user instance and raising limits

2017-11-20 Thread Lennart Poettering
On Mo, 20.11.17 09:47, Jeff Solomon ([email protected]) wrote: > I guess the answer is "no." :) > > This is Ubuntu 16.04. On CentOS7.3, pam_limits is part of systemd-user > through system-auth > > Here is /etc/pam.d/systemd-user from my Ubuntu system: > > # This file is part of systemd. >

Re: [systemd-devel] systemd user instance and raising limits

2017-11-20 Thread Jeff Solomon
I have checked the snippets. "common-account" only deal with account settings. "common-session-interactive" does not include a pam_limits entry. On Mon, Nov 20, 2017 at 9:49 AM, Lennart Poettering wrote: > On Mo, 20.11.17 09:47, Jeff Solomon ([email protected]) wrote: > > > I guess the answ

Re: [systemd-devel] systemd user instance and raising limits

2017-11-20 Thread Jeff Solomon
I guess the answer is "no." :) This is Ubuntu 16.04. On CentOS7.3, pam_limits is part of systemd-user through system-auth Here is /etc/pam.d/systemd-user from my Ubuntu system: # This file is part of systemd. # # Used by systemd --user instances. @include common-account session required pam_s

Re: [systemd-devel] systemd user instance and raising limits

2017-11-20 Thread Jeff Solomon
Lennart, Your explanation sounds great but it's just not what I'm seeing. My [email protected] has "PAMName=systemd-user" in the [Service] section. I have setup limits for the user in /etc/security/limits.d/foo.conf. I have no other limit overrides in any other systemd file. Whether I reboot or "s

Re: [systemd-devel] systemd user instance and raising limits

2017-11-20 Thread Lennart Poettering
On Mo, 20.11.17 09:20, Jeff Solomon ([email protected]) wrote: > Lennart, > > Your explanation sounds great but it's just not what I'm seeing. > > My [email protected] has "PAMName=systemd-user" in the [Service] section. > > I have setup limits for the user in /etc/security/limits.d/foo.conf.

Re: [systemd-devel] systemd user instance and raising limits

2017-11-20 Thread Lennart Poettering
On Mo, 20.11.17 08:32, Jeff Solomon ([email protected]) wrote: > I am using lingering and I have issued "systemctl restart user@" 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 "[email protected]" or

Re: [systemd-devel] systemd user instance and raising limits

2017-11-20 Thread Jeff Solomon
I am using lingering and I have issued "systemctl restart user@" 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 "[email protected]" or in "/etc/systemd/system/[email protected]/whatever.conf" I see that they are resp

Re: [systemd-devel] systemd user instance and raising limits

2017-11-20 Thread Lennart Poettering
On So, 19.11.17 16:57, Jeff Solomon ([email protected]) wrote: > > I didn't think that systemd paid one bit of attention to the settings > >> controlled by pam_limits? > >> > > > > The user@ instance runs user-controlled processes, much like cron would, > > so its service unit has PAM enabled

Re: [systemd-devel] systemd user instance and raising limits

2017-11-19 Thread Jeff Solomon
> I didn't think that systemd paid one bit of attention to the settings >> controlled by pam_limits? >> > > The user@ instance runs user-controlled processes, much like cron would, > so its service unit has PAM enabled as well. > When I change pam_limits for a user via a file /etc/security/limits.

Re: [systemd-devel] systemd user instance and raising limits

2017-11-19 Thread Mantas Mikulėnas
On Mon, Nov 20, 2017, 02:27 Jeff Solomon wrote: > Understood. > > I didn't think that systemd paid one bit of attention to the settings > controlled by pam_limits? > The user@ instance runs user-controlled processes, much like cron would, so its service unit has PAM enabled as well. > I'm only

Re: [systemd-devel] systemd user instance and raising limits

2017-11-19 Thread Jeff Solomon
Understood. I didn't think that systemd paid one bit of attention to the settings controlled by pam_limits? I'm only interested in a user instance that is lingering and operates outside of a session. My goal is that the child processes of the user instance will have limits that I set. If I under

Re: [systemd-devel] systemd user instance and raising limits

2017-11-19 Thread Mantas Mikulėnas
On Sun, Nov 19, 2017, 22:01 Jeff Solomon wrote: > Hi, > > Two questions. > > I want to raise the "number of files" limits for the user instance. > > First, I set DefaultLimitNOFILE to something higher than the global system > default in /etc/systemd/user.conf and I rebooted. > > Then I confirmed

[systemd-devel] systemd user instance and raising limits

2017-11-19 Thread Jeff Solomon
Hi, Two questions. I want to raise the "number of files" limits for the user instance. First, I set DefaultLimitNOFILE to something higher than the global system default in /etc/systemd/user.conf and I rebooted. Then I confirmed that the setting has taken effect: "systemctl --user show" showed