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
> >
>
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
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
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.
>
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
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
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
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.
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
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
That is good to hear and I look forward to seeing it enabled in el8!
On Mon, Nov 20, 2017 at 7:43 AM, Lukas Nykryn wrote:
> That comment explains why --user was removed when centos7 was released.
> Although now we know that it will remain as it is in upstream, we don't
> plan to revert the remov
On Fr, 17.11.17 17:11, Shekhar arya ([email protected]) wrote:
> Hi
>
> I have upgraded my systemd from older version v195 (used in poky 1.6) to
> v225 to resolve some of the memory leak issues. I have resolved all the
> dependencies while compilation and now system boots fine. However, af
That comment explains why --user was removed when centos7 was released.
Although now we know that it will remain as it is in upstream, we don't
plan to revert the removal in el7, since we are afraid of potential
regressions that it might cause. I personally saw couple of logs where
users had some a
On So, 19.11.17 00:18, דניאל חומדוב ([email protected]) wrote:
> root@host:/home/user# systemctl status [email protected]
>
> ● [email protected] - OpenVPN connection to openvpn
>
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
15 matches
Mail list logo
