Re: [arch-general] systemctl daemon-reexec - anything else needed after systemd update?
Hi David, > Most of the Arch systems I have running are servers, so it is fairly > easy just to scan the upgrade list and note which applications I need > to restart. You do better than me then. I get surprised by some of the deleted /usr/lib/* that are still loaded by running executables. -- Cheers, Ralph. https://plus.google.com/+RalphCorderoy
Re: [arch-general] systemctl daemon-reexec - anything else needed after systemd update?
On 12/19/2018 05:57 PM, Ralph Corderoy wrote:
> Hi David,
>
> Robin wrote:
>>> Is there anything else needed other than daemon-reexec when there is
>>> an update to systemd itself?
>>
>> https://git.archlinux.org/svntogit/packages.git/tree/trunk/systemd.install?h=packages/systemd#n80
>
> You might be interested in what running process have deleted files still
> open, perhaps because a package upgrade has installed a new version, or
> caused a updated version to be generated. A quickly knocked together
> pipeline I use is
>
> sudo -i lsof -n +c0 |
> sed -n '1{p;d}; /DEL/{p;d}; / (deleted)$/{p;d}' |
> egrep -v '
> /(SYSV|dev/shm/org\.(chromium\...|mozilla\.ipc\.[0-9]+\.[0-9]+)|memfd:pulseaudio|tmp/#[0-9]{5,7})\>'
> |
> sed '1{h; d}; 2{x; G}'
>
> Not all the entries it shows matter, of course. It's up to the reader
> to parse and, say, decide to restart postfix.
>
Robin, Ralph,
Thanks. Glad to know it is already handled in post_upgrade(). Interesting
use of lsof and the parse of files open. Most of the Arch systems I have
running are servers, so it is fairly easy just to scan the upgrade list and
note which applications I need to restart.
The interesting part is that I have religiously done 'daemon-reload' if I
noticed any running unit files updated. Since post_upgrade() calls
daemon-reexex -- I don't even need to do that anymore if systemd is among the
ugrades :)
It may be worth adding to the systemd wiki page. It is silent about
daemon-reexec and the fact that is called with post_upgrade(). (it's there in
the PKGBUILD, and the post_install output "Reloading system manager
configuration...", but I didn't snap to the fact that "reloading" was doing
the reexec) Learning has occurred.
--
David C. Rankin, J.D.,P.E.
Re: [arch-general] systemctl daemon-reexec - anything else needed after systemd update?
Hi David,
Robin wrote:
> > Is there anything else needed other than daemon-reexec when there is
> > an update to systemd itself?
>
> https://git.archlinux.org/svntogit/packages.git/tree/trunk/systemd.install?h=packages/systemd#n80
You might be interested in what running process have deleted files still
open, perhaps because a package upgrade has installed a new version, or
caused a updated version to be generated. A quickly knocked together
pipeline I use is
sudo -i lsof -n +c0 |
sed -n '1{p;d}; /DEL/{p;d}; / (deleted)$/{p;d}' |
egrep -v '
/(SYSV|dev/shm/org\.(chromium\...|mozilla\.ipc\.[0-9]+\.[0-9]+)|memfd:pulseaudio|tmp/#[0-9]{5,7})\>'
|
sed '1{h; d}; 2{x; G}'
Not all the entries it shows matter, of course. It's up to the reader
to parse and, say, decide to restart postfix.
--
Cheers, Ralph.
https://plus.google.com/+RalphCorderoy
Re: [arch-general] systemctl daemon-reexec - anything else needed after systemd update?
On 12/19/18 11:52 PM, David C. Rankin wrote: > Archdevs, > > After todays update to systemd-239.370-1, there was nothing that would have > prompted a reboot (like a kernel update), so I simply wanted to restart the > daemon. From the systemctl man page, the daemon-reexec option seems like the > logical way, > > "...This command is of little use except for debugging and package upgrades. > Sometimes, it might be helpful as a heavy-weight daemon-reload." https://git.archlinux.org/svntogit/packages.git/tree/trunk/systemd.install?h=packages/systemd#n80 > Is there anything else needed other than daemon-reexec when there is an > update to systemd itself? > You don't have to do anything. -- Rob (coderobe) O< ascii ribbon campaign - stop html mail - www.asciiribbon.org signature.asc Description: OpenPGP digital signature
[arch-general] systemctl daemon-reexec - anything else needed after systemd update?
Archdevs, After todays update to systemd-239.370-1, there was nothing that would have prompted a reboot (like a kernel update), so I simply wanted to restart the daemon. From the systemctl man page, the daemon-reexec option seems like the logical way, "...This command is of little use except for debugging and package upgrades. Sometimes, it might be helpful as a heavy-weight daemon-reload." Is there anything else needed other than daemon-reexec when there is an update to systemd itself? -- David C. Rankin, J.D.,P.E.
