Comment 3 for bug 2051766

I'm guessing the glibc security update is the one that caused all those services to restart.

Is that something you can reproduce reliably, e.g. using `apt reinstall libc6`?
I might have an idea that could solve this problem without having to special-case networking service, but that's a theory and I'd need to actually test it out.

The gist of it would be to replace the single `systemctl restart` call by multiple ones. My underlying assumption is that systemd will batch up all those services for restart in parallel (unless there is an explicit ordering in the system files), whereas using dedicated restart calls means that, assuming the services are properly written to signal themselves as ready when they actually are, any service should always have a stable environment to use during its startup.