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 systemd process simply reexecutes itself. It doesn't fork, so it
doesn't get a new PID.
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.
This won't pick up changes to the user@.service unit loaded into the
system-wide systemd instance. There shouldn't be any reason to change
this unit.
_______________________________________________
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel
