Bug#974730: systemd 247~rc2-2 install crashed several system

[Michael Biebl]

Am Samstag, den 14.11.2020, 17:00 +0100 schrieb Eric Valette:
> Le 14/11/2020 à 13:54, Michael Biebl a écrit :
> 
> > Are you configuring your NAS with ifupdown (using allow-hotplug).
> 
> Yes indeed. I use a fixed address outside my DHCP dynamic range so
> no 
> need to something sophisticated and no graphical interface so no
> need 
> for network-manager and I hate transfering all the control to
> systemd...
> 
> allow-hotplug eth0
> iface eth0 inet static
> 	....

Ok, thanks for confirming.
This means ifup at .service is used which has

BindsTo=sys-subsystem-net-devices-%i.device

and further confirms my theory, that this issue is related to units
with BindsTo=<device> being stopped (and not restarted) during a
daemon-reexec due to the udev tags related changes.

> 
> This is very bad for remote managed Linux system with difficult
> access 
> like in data center...

In a data center (without remote access) I would recommend *not* using
unstable, and experimental even more so. I uploaded this version to
experimental for a reason.

> > Fwiw, that sounds very much like
> > https://github.com/systemd/systemd/issues/17605#issuecomment-727187837
> > 
> 
> While systemd does offers a far superior boot time by dependency and 
> //ism, this will soon become unmanageable I fear.
> 

While I can understand if you are pissed when a remote machine has
become unreachable, this remark is unnecessary.
Please don't, this really drains my motivation.


Regards,
Michael
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: This is a digitally signed message part
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20201114/46d921e0/attachment.sig>