[TW] Restarting systemd after zypper dup
Following zypper dup, :~> sudo zypper ps -s The following running processes use deleted files: PID | PPID | UID | User | Command | Service -----+------+------+------+---------+-------- 1 | 0 | 0 | root | systemd | 1857 | 1 | 1000 | bob | systemd | 1858 | 1857 | 1000 | bob | systemd | what is the correct way to restart these processes? I have tried :~> sudo systemctl daemon-reload :~> sudo systemctl --user daemon-reload :~> systemctl --user daemon-reload without success Regards Bob -- Bob Williams
Am Samstag, 2. Juli 2022, 08:41:44 CEST schrieb Bob Williams:
Following zypper dup,
:~> sudo zypper ps -s
The following running processes use deleted files:
PID | PPID | UID | User | Command | Service -----+------+------+------+---------+-------- 1 | 0 | 0 | root | systemd | 1857 | 1 | 1000 | bob | systemd | 1858 | 1857 | 1000 | bob | systemd |
what is the correct way to restart these processes?
I have tried
:~> sudo systemctl daemon-reload :~> sudo systemctl --user daemon-reload :~> systemctl --user daemon-reload
"systenctl daemon-rexec" is the actual restart of systemd, that should do it. Cheers MH -- Mathias Homann Mathias.Homann@openSUSE.org Jabber (XMPP): lemmy@tuxonline.tech Matrix: @mathias:eregion.de IRC: [Lemmy] on freenode and ircnet (bouncer active) keybase: https://keybase.io/lemmy gpg key fingerprint: 8029 2240 F4DD 7776 E7D2 C042 6B8E 029E 13F2 C102
On Sat, 02 Jul 2022 10:03:54 +0200 Mathias Homann wrote:
Am Samstag, 2. Juli 2022, 08:41:44 CEST schrieb Bob Williams:
Following zypper dup,
:~> sudo zypper ps -s
The following running processes use deleted files:
PID | PPID | UID | User | Command | Service -----+------+------+------+---------+-------- 1 | 0 | 0 | root | systemd | 1857 | 1 | 1000 | bob | systemd | 1858 | 1857 | 1000 | bob | systemd |
what is the correct way to restart these processes?
I have tried
:~> sudo systemctl daemon-reload :~> sudo systemctl --user daemon-reload :~> systemctl --user daemon-reload
"systenctl daemon-rexec" is the actual restart of systemd, that should do it.
Cheers MH
Thanks. I noticed this command in the manpage, but it seemed to discourage its use: daemon-reexec Reexecute the systemd manager. This will serialize the manager state, reexecute the process and deserialize the state again. This command is of little use except for debugging and package upgrades. Sometimes, it might be helpful as a heavy-weight daemon-reload. While the daemon is being reexecuted, all sockets systemd listening on behalf of user configuration will stay accessible. -- Bob Williams
On 2022-07-02 08:41, Bob Williams wrote:
Following zypper dup,
:~> sudo zypper ps -s The following running processes use deleted files:
PID | PPID | UID | User | Command | Service -----+------+------+------+---------+-------- 1 | 0 | 0 | root | systemd | 1857 | 1 | 1000 | bob | systemd | 1858 | 1857 | 1000 | bob | systemd |
what is the correct way to restart these processes?
Reboot. -- Cheers / Saludos, Carlos E. R. (from Elesar, using openSUSE Leap 15.3)
On Sat, 2 Jul 2022 11:06:39 +0200 Carlos E. R. wrote:
On 2022-07-02 08:41, Bob Williams wrote:
Following zypper dup,
:~> sudo zypper ps -s The following running processes use deleted files:
PID | PPID | UID | User | Command | Service -----+------+------+------+---------+-------- 1 | 0 | 0 | root | systemd | 1857 | 1 | 1000 | bob | systemd | 1858 | 1857 | 1000 | bob | systemd |
what is the correct way to restart these processes?
Reboot.
But it told me: No core libraries or services have been updated since the last system boot. Reboot is probably not necessary. -- Bob Williams
On 7/2/22 11:25, Bob Williams wrote:
On Sat, 2 Jul 2022 11:06:39 +0200 Carlos E. R. wrote:
On 2022-07-02 08:41, Bob Williams wrote:
Following zypper dup,
:~> sudo zypper ps -s The following running processes use deleted files:
PID | PPID | UID | User | Command | Service -----+------+------+------+---------+-------- 1 | 0 | 0 | root | systemd | 1857 | 1 | 1000 | bob | systemd | 1858 | 1857 | 1000 | bob | systemd |
what is the correct way to restart these processes?
Reboot.
But it told me:
No core libraries or services have been updated since the last system boot. Reboot is probably not necessary.
IMHO that's just a deficiency of zypper ps. => reboot Ciao, Michael.
On 2022-07-02 11:25, Bob Williams wrote:
On Sat, 2 Jul 2022 11:06:39 +0200 Carlos E. R. wrote:
On 2022-07-02 08:41, Bob Williams wrote:
...
what is the correct way to restart these processes?
Reboot.
But it told me:
No core libraries or services have been updated since the last system boot. Reboot is probably not necessary.
As you can see, zypper ps is not always correct. Just reboot; wasting time looking for a "better" way to restart the minimum processes is not worth it, and provides no peace of mind. -- Cheers / Saludos, Carlos E. R. (from Elesar, using openSUSE Leap 15.3)
On 7/2/22 01:41, Bob Williams wrote:
:~> sudo systemctl daemon-reload
Is all that is required to reload the daemon as in restarting it. zypper ps isn't the brightest bulb in the room. Many systemd implementation automatically hook "systemctl daemon-reload" on systemd upgrade (I haven't looked at the openSUSE .spec file for it, but I would be surprised if it didn't) After I run the daemon-reload, if zypper ps is still unhappy, I ignore it. It's not windows, no need to reboot except for kernel updates. (or unexplained Plasma or Gnome issues....) -- David C. Rankin, J.D.,P.E.
On Sat, 2 Jul 2022 19:14:42 -0500 David C. Rankin wrote:
On 7/2/22 01:41, Bob Williams wrote:
:~> sudo systemctl daemon-reload
Is all that is required to reload the daemon as in restarting it. zypper ps isn't the brightest bulb in the room. Many systemd implementation automatically hook "systemctl daemon-reload" on systemd upgrade (I haven't looked at the openSUSE .spec file for it, but I would be surprised if it didn't)
After I run the daemon-reload, if zypper ps is still unhappy, I ignore it. It's not windows, no need to reboot except for kernel updates. (or unexplained Plasma or Gnome issues....)
I usually find that daemon-reload doesn't affect one or all of the user instances of systemd. I shall try your advice. If something doesn't work later on, I can always reboot then. Thank you. -- Bob Williams
On 2022-07-03 07:06, Bob Williams wrote:
On Sat, 2 Jul 2022 19:14:42 -0500 David C. Rankin wrote:
On 7/2/22 01:41, Bob Williams wrote:
:~> sudo systemctl daemon-reload
Is all that is required to reload the daemon as in restarting it. zypper ps isn't the brightest bulb in the room. Many systemd implementation automatically hook "systemctl daemon-reload" on systemd upgrade (I haven't looked at the openSUSE .spec file for it, but I would be surprised if it didn't)
After I run the daemon-reload, if zypper ps is still unhappy, I ignore it. It's not windows, no need to reboot except for kernel updates. (or unexplained Plasma or Gnome issues....)
I usually find that daemon-reload doesn't affect one or all of the user instances of systemd. I shall try your advice. If something doesn't work later on, I can always reboot then. Thank you.
Frankly, it is far easier to reboot. Yes, Linux is not Windows but still, restarting updated "things" is not that easy, some must be done in an exact sequence, and some do not restart perfectly. Strange things do sometimes happen, so the faster route, no thinking needed, no hassle, is just rebooting. And if you can not reboot, simply do not update. Delay the update till you can reboot if needed. -- Cheers / Saludos, Carlos E. R. (from Elesar, using openSUSE Leap 15.3)
On 2022-07-03 09:11, Carlos E. R. wrote:
On 2022-07-03 07:06, Bob Williams wrote:
On Sat, 2 Jul 2022 19:14:42 -0500 David C. Rankin wrote:
On 7/2/22 01:41, Bob Williams wrote:
:~> sudo systemctl daemon-reload
Is all that is required to reload the daemon as in restarting it. zypper ps isn't the brightest bulb in the room. Many systemd implementation automatically hook "systemctl daemon-reload" on systemd upgrade (I haven't looked at the openSUSE .spec file for it, but I would be surprised if it didn't)
After I run the daemon-reload, if zypper ps is still unhappy, I ignore it. It's not windows, no need to reboot except for kernel updates. (or unexplained Plasma or Gnome issues....)
I usually find that daemon-reload doesn't affect one or all of the user instances of systemd. I shall try your advice. If something doesn't work later on, I can always reboot then. Thank you.
Frankly, it is far easier to reboot. Yes, Linux is not Windows but still, restarting updated "things" is not that easy, some must be done in an exact sequence, and some do not restart perfectly. Strange things do sometimes happen, so the faster route, no thinking needed, no hassle, is just rebooting.
And if you can not reboot, simply do not update. Delay the update till you can reboot if needed.
I hate agreeing with Carlos, I really do, but he’s absolutely right here The truths he shares here are some of those firmly embraced by MicroOS, which doesn’t even write to the running system to avoid causing the kind of random problems mentioned elsewhere in this thread. Better to reboot from a known consistent system to a new consistent system rather than swapping around libraries, drivers, and the like while things are running and perhaps introducing untestable conditions as a result. -- Richard Brown Linux Distribution Engineer - Future Technology Team SUSE Software Solutions Germany GmbH, Frankenstraße 146, D-90461 Nuremberg, Germany (HRB 36809, AG Nürnberg) Managing Directors/Geschäftsführer: Ivo Totev, Andrew Myers, Andrew McDonald, Martje Boudien Moerman
On 03.07.22 02:14, David C. Rankin wrote:
On 7/2/22 01:41, Bob Williams wrote:
:~> sudo systemctl daemon-reload
Is all that is required to reload the daemon as in restarting it. zypper ps isn't the brightest bulb in the room. Many systemd implementation automatically hook "systemctl daemon-reload" on systemd upgrade (I haven't looked at the openSUSE .spec file for it, but I would be surprised if it didn't)
After I run the daemon-reload, if zypper ps is still unhappy, I ignore it. It's not windows, no need to reboot except for kernel updates. (or unexplained Plasma or Gnome issues....)
Well, daemon-reload does only reconfigure systemd (for example it activates new/changed service files IIUC). If you have updated libraries that are in use by systemd, you need to restart it, which is what "daemon-reexec" does. And even if there is no strict need to do this, I personally like to do that to get rid of the disk space pinned by the deleted-but-still-in-use libraries. AND strange things *can* happen if you don't but they are pretty obscure usually so not much to worry for the "normal" user. -- Stefan Seyfried "For a successful technology, reality must take precedence over public relations, for nature cannot be fooled." -- Richard Feynman
participants (7)
-
Bob Williams -
Carlos E. R. -
David C. Rankin -
Mathias Homann -
Michael Ströder -
Richard Brown -
Stefan Seyfried