[systemd-devel] Hints for upgrading systemd on a running system

Lennart Poettering lennart at poettering.net
Tue Feb 20 22:30:50 UTC 2018


On Di, 20.02.18 20:06, Reindl Harald (h.reindl at thelounge.net) wrote:

> 
> 
> Am 20.02.2018 um 20:00 schrieb Paul Menzel:
> > Dear systemd folks,
> > 
> > We finally are going to upgrade from a very old systemd version 27 from
> > 2011 to the current systemd v237. (Historical reasons.)
> 
> hopefully you have a working backup
> 
> > Anyway, I already was told about `systemctl daemon-reexec`, and we got
> > it working.
> 
> the "reexec" is misleading because it's not possible to terminate PID1 and
> start it again on a running system with a new binary

Hmm? "systemctl daemon-reexec" is supposed to support upgrades between
systemd versions. Doing massive jumps v27 → v237 in one go isn't
precisely well tested, but smaller ones should work quite well.

Lennart

-- 
Lennart Poettering, Red Hat


More information about the systemd-devel mailing list