News for hackers. Stuff that matters.
Re:Running systemd without systemd-journald by egberts1 on Sunday June 19, 2022 @11:55PM (#31806126)
Its never a good systemd-networkd default to be killing daemon whenever a netdev goes “cricket”.
Re:Running systemd without systemd-journald by viraptor on Monday June 20, 2022 @12:19AM (#31806237)
It's not a networkd default. Networkd doesn't kill or even care about other services. The setting exists on the service's unit side. You have to explicitly specify how you want to depend on networking.
Re:Running systemd without systemd-journald by egberts1 on Monday June 20, 2022 @12:26AM (#31806273)
Try it. Pull the Ethernet cable.
Re:Running systemd without systemd-journald by viraptor on Monday June 20, 2022 @12:36AM (#31806331)
I do that every day moving between WiFi and plugged in Ethernet. It seems you're misunderstanding what exactly is killing processes in your case. Try to collect the logs and maybe ask on serverfault. I promise networkd is not killing your processes and if you don't have strict dependencies in your unit file, systemd is unlikely to do that either.
Re:Running systemd without systemd-journald by crazy_hombre on Monday June 20, 2022 @12:30PM (#31812308)
An ethernet interface is not a netdev. Netdevs are always virtual interfaces.
Re:Running systemd without systemd-journald by egberts1 on Monday June 20, 2022 @12:37AM (#31806337)
it is a good thing you have no states to care for.