4 ms·
Its never a good systemd-networkd default to be killing daemon whenever a netdev goes “cricket”.
by egberts1 4y ago
Its never a good systemd-networkd default to be killing daemon whenever a netdev goes “cricket”.
- dralley 4y agoBut that's just it, to say this just demonstrates you don't understand the systemd service model. There is no "system default" in the loop here at all. The service told systemd that it cannot operate without netdev, and systemd behaved accordingly. If the config was written more appropriately, it would have behaved accordingly. The "default" is what you had written in the unit file.