systemd can run its daemon as a user and manage services for that user.
The user services can be restarted in much the same way as system services.
It would be great that instead of listing these daemons in the outdated
binaries section, needrestart would list the commands to restart them:
sudo -u uid systemctl --user daemon-reexec
sudo -u uid systemctl --user restart name.service other.service
# systemctl status
● chianamo
State: running
Jobs: 0 queued
Failed: 0 units
Since: ...
CGroup: /
...
└─user.slice
├─user-1000.slice
│ ├─us...@1000.service
│ │ ├─gpg-agent.service
│ │ │ └─1931 /usr/bin/gpg-agent --supervised
│ │ ├─dirmngr.service
│ │ │ └─20314 /usr/bin/dirmngr --daemon --homedir /home/pabs/.gnupg
│ │ └─init.scope
│ │ ├─1927 /lib/systemd/systemd --user
│ │ └─1929 (sd-pam)
...
# needrestart
Scanning processes...
Scanning candidates...
Scanning linux images...
...
Services to be restarted:
...
Services being skipped:
...
No containers need to be restarted.
User sessions running outdated binaries:
Debian-gdm @ user manager service: systemd[1527]
pabs @ session #2: ...
pabs @ user manager service: systemd[1927]
root @ session #306: gpg-agent[14884]
root @ user manager service: systemd[16906]
--
bye,
pabs