I've hit a similar problem, though it's net.bridge.bridge-nf-call- iptables that I care about.
It's not because it's running too early though, it's not running at all. I confirmed this by adding some echos to a log file to the script in /etc/init/procps.conf. It appears to be broken in both karmic and maverick. I think this must be an upstart or mountall bug. ** Package changed: procps (Ubuntu) => upstart (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/690433 Title: procps starts too early to correctly set net.netfilter.nf_conntrack_acct -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
