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.
** Also affects: needrestart (Ubuntu Noble)
Importance: Undecided
Status: New
** Also affects: needrestart (Ubuntu Oracular)
Importance: Undecided
Status: New
** Changed in: needrestart (Ubuntu Noble)
Assignee: (unassigned) => Simon Chopin (schopin)
** Changed in: needrestart (Ubuntu Oracular)
Assignee: (unassigned) => Simon Chopin (schopin)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2051766
Title:
needrestart should priorize and wait for network and DNS when
restarting services
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/needrestart/+bug/2051766/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
