*** This bug is a duplicate of bug 771372 ***
https://bugs.launchpad.net/bugs/771372
This is still a problem in 16.04 LTS/xenial. I lost a whole workday
chasing this down after an upgrade. I don't think it's a duplicate of
771372, as the above discussion indicates there is no "right" place to
run procps, and 771372 works on that presumption. Instead, the start-up
process needs to be reworked, or at least the network-related settings
need to be reassigned to the network start-up process instead of living
in procps. With the increased use of bridges (KVM, LXC, etc.), we
should have a smooth start-up process for bridges and bridge-related
settings.
I confess I don't understand all the complexities others apparently see.
We need someone that really understands the relevant start-up processes
to architect a good solution. What can we do to get a little attention
on this problem?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/50093
Title:
Some sysctl's are ignored on boot
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/procps/+bug/50093/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
