All documentation on the net referring to changing certain settings in /etc/sysctl.conf such as net.ipv4.netfilter.ip_conntrack_max is wrong for Ubuntu. In addition, workarounds suggesting that ordering of module load vs. sysctl.conf execution can be helped by i.e. putting ip_conntrack into /etc/modules also do not work.
I'm sure on some level this is Low priority - aka bury for 5 years and never look at it again - and I can appreciate that this is not a simple problem to properly solve. But left as is, this is just another mine laid in the field for sysadmins foolish enough to use Ubuntu Server. I respectfully suggest that it might be useful to make multiple attempts to run sysctl -p at various milestones during the boot process. -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs