Re: [systemd-devel] systemd user instance not working in only one account, XDG_RUNTIME_DIR not being set

On Tue, Apr 11, 2023, 03:41 Chandler wrote: > systemd has been working great here, system-wide as well as in all user > instances except one. I'm not exactly sure what all the steps are in > the process to get a systemd user instance running. The directory > /run/user/$UID was not being

[systemd-devel] systemd user instance not working in only one account, XDG_RUNTIME_DIR not being set

systemd has been working great here, system-wide as well as in all user instances except one. I'm not exactly sure what all the steps are in the process to get a systemd user instance running. The directory /run/user/$UID was not being created, though. I made some progress by running `systemctl

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

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/ >

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

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

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

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,

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

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 (jsolomon8...@gmail.com)

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

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

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

Lennart, Your explanation sounds great but it's just not what I'm seeing. My user@.service 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

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

On Mo, 20.11.17 09:20, Jeff Solomon (jsolomon8...@gmail.com) wrote: > Lennart, > > Your explanation sounds great but it's just not what I'm seeing. > > My user@.service 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

On Mo, 20.11.17 08:32, Jeff Solomon (jsolomon8...@gmail.com) 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 "user@.service" or

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

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 "user@.service" or in "/etc/systemd/system/user@.service.d/whatever.conf" I see that they are

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

On So, 19.11.17 16:57, Jeff Solomon (jsolomon8...@gmail.com) 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

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

> 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

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

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

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

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

[systemd-devel] systemd user instance and raising limits

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"

Re: [systemd-devel] systemd user instance

On 05/06/2013 10:14 PM, Kai Krakow wrote: Jóhann B. Guðmundsson johan...@gmail.com schrieb: But now I want to (and need to) give some users cron-like abilities. I discovered that systemd supports user instances - perfect! Then install cronie... That's the obvious solution but a little bit

Re: [systemd-devel] systemd user instance

Kok, Auke-jan H auke-jan.h@intel.com schrieb: [Service] User=%I PAMName=systemd-shared ^^ this line is the cause of your problems, as the /etc/pam.d/systemd-shared file does not exist. I thought this is virtually profided by pam_systemd.so? But I may try your suggestion. Regards,

Re: [systemd-devel] systemd user instance

Jóhann B. Guðmundsson johan...@gmail.com schrieb: But now I want to (and need to) give some users cron-like abilities. I discovered that systemd supports user instances - perfect! Then install cronie... That's the obvious solution but a little bit counter-productive with respect to my

Re: [systemd-devel] systemd user instance

Well, actually the timers are a nice benefit only. We want to control user- initiated background-services for a web application server with this and cron hasn't been our best friend for this in the past. David Strauss da...@davidstrauss.net schrieb: I don't recommend spawning user instances of

[systemd-devel] systemd user instance

Hey list, I've built a server with systemd and it really worked out well. Fast booting (that means shorter maintenance times) and most important: Reliable service teardown and auto-restarts of crashed services. And yeah, I love the journal. I'm logging everything there. But now I want to (and

Re: [systemd-devel] systemd user instance

On 05/06/2013 09:44 PM, Kai Krakow wrote: But now I want to (and need to) give some users cron-like abilities. I discovered that systemd supports user instances - perfect! Then install cronie... JBG ___ systemd-devel mailing list

Re: [systemd-devel] systemd user instance

Jóhann B. Guðmundsson johan...@gmail.com schrieb: But now I want to (and need to) give some users cron-like abilities. I discovered that systemd supports user instances - perfect! Then install cronie... That's the obvious solution but a little bit counter-productive with respect to my

Re: [systemd-devel] systemd user instance

I don't recommend spawning user instances of systemd just for their timer units to run. Each instance comes with a few MB of overhead, and you'll have no fun trying to spawn sessions in a way isolated from (but somehow integrated with) the PAM session initialization process. On Mon, May 6, 2013

Re: [systemd-devel] systemd user instance

On Mon, May 6, 2013 at 2:44 PM, Kai Krakow hurikha...@gmail.com wrote: Hey list, I've built a server with systemd and it really worked out well. Fast booting (that means shorter maintenance times) and most important: Reliable service teardown and auto-restarts of crashed services. And yeah, I