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 the reason you specify Michael. The user@.service file might change and we want to make use of it immediately. Also, we're only using lingering, so logging out and in doesn't apply to us. On Fri, Nov 17, 2017 at 3:16 PM, Michael Chapman <m...@very.puzzling.org> wrote: > 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: > > systemctl --user daemon-reexec > > This serializes state across the re-execution, so services running in the > instance are not killed. > > There's few reasons a user might want to do this however. The only one I > can think of is where the admin had updated the systemd package and the > user wanted to make use of it immediately. >
_______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel