Re: [systemd-devel] systemctl --user user can't restart their own service?

2017-11-17 Thread Michael Chapman
On Sat, 18 Nov 2017, Jeff Solomon wrote: When I run: systemctl --user daemon-reexec I see that the daemon gets a --deserialize flag in it command line on "top" but the PID is not any different. I guess I don't need the PID to change if the process picks up any changes to its unit file. The

Re: [systemd-devel] systemctl --user user can't restart their own service?

2017-11-17 Thread Jeff Solomon
When I run: systemctl --user daemon-reexec I see that the daemon gets a --deserialize flag in it command line on "top" but the PID is not any different. I guess I don't need the PID to change if the process picks up any changes to its unit file. I would want to use this command for exactly th

Re: [systemd-devel] systemctl --user user can't restart their own service?

2017-11-17 Thread Michael Chapman
On Sat, 18 Nov 2017, Jeff Solomon wrote: Hi, Is it by-design that a user can't restart their own user service? If they aren't a lingering user, they'll get a new systemd instance if they completely log out and back in again. Alternatively, they can restart the running instance with: syst

Re: [systemd-devel] systemctl --user user can't restart their own service?

2017-11-17 Thread Kai Krakow
Am Fri, 17 Nov 2017 10:00:35 -0800 schrieb Jeff Solomon : > Hi, > > Is it by-design that a user can't restart their own user service? > > I have worked around this by doing the following: > > Override /lib/systemd/system/user@.service with a new file: > > /etc/systemd/system/user@.service > >

[systemd-devel] systemctl --user user can't restart their own service?

2017-11-17 Thread Jeff Solomon
Hi, Is it by-design that a user can't restart their own user service? I have worked around this by doing the following: Override /lib/systemd/system/user@.service with a new file: /etc/systemd/system/user@.service I could have left out the if I wanted the override to apply to all users, but i

Re: [systemd-devel] systemctl --user roadmap question

2017-11-17 Thread Lennart Poettering
On Fr, 17.11.17 09:20, Jeff Solomon (jsolomon8...@gmail.com) wrote: > Hi, > > RHEL removed support for systemd "user services" because they said: > > "Basically we don't know if systemd --user will stay in systemd as is right > now. > So we have decided to disable it completely so we will not hi

[systemd-devel] systemctl --user roadmap question

2017-11-17 Thread Jeff Solomon
Hi, RHEL removed support for systemd "user services" because they said: "Basically we don't know if systemd --user will stay in systemd as is right now. So we have decided to disable it completely so we will not hit regression in future versions of centos." That statement was made 18 months ago.

Re: [systemd-devel] moved from systemd 195 to 225, unable to start custom services.

2017-11-17 Thread Zbigniew Jędrzejewski-Szmek
On Fri, Nov 17, 2017 at 05:11:26PM +0530, Shekhar arya 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, after > the

[systemd-devel] moved from systemd 195 to 225, unable to start custom services.

2017-11-17 Thread Shekhar arya
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, after the boot is complete, systemd is not able to start services present in /lib/s

[systemd-devel] [issue while upgrading systemd]

2017-11-17 Thread Shekhar arya
Hi, I have moved from older version of systemd (part of poky 1.6) to systemd 225 (poky 1.6). I have resolved all dependencies while compilation. However, -- regards, - Shekhar ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://