Hi, I have been running some provocative tests on a systemd based OS with Clould99 and I have found out that systemd-networkd daemon would not recover after killing it with SIGTERM. This is quite understandable since the systemd-networkd.service is configured with "Restart=on-failure".
Is that service configured that way on purpose or it was just not considered that systemd-networkd daemon could erroneously exit with zero or be killed spuriously with SIGTERM? If the config would be changed to "Restart=always" then this case would be covered as well. At least from service availability that would be better option else it would not recover at all. Or is there some case when this would not be desired? Jan _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
