Ubuntu
procps package

  1. Bug #50093
  2. Comment #3

Comment 3 for bug 50093

Revision history for this message
jollyroger (jeffrey-crawford) wrote : Re: Some sysctl's are ignored on boot

This seems pretty old and I'm not sure against which version of Ubuntu it was filed against (Sorry kinda new to this bug system) however to appears that the problem is two fold. I'm using karmic right now which uses upstart. I've had trouble getting the following settings to work:

=={/etc/sysctl.conf}==
net.bridge.bridge-nf-call-arptables = 0
net.bridge.bridge-nf-call-iptables = 0
net.bridge.bridge-nf-call-ip6tables = 0

kernel.shmmax = 68719476736
kernel.shmall = 4294967296
===

The upstart system had the procps starting after the event "virtual-filesystems" which is triggered by /etc/init/mountall.conf. It appears that due to the fact that many kernel modules are not yet loaded the, for example "bridge.ko", the entries above do not exist yet in sysctl/procfs, so I changed "/etc/init/procps.conf" "start" line to read "start on starting network-interface" This allows the bridge modules to be loaded and and available when procps is allowed to run. Additionally I modified the procps.conf script line to include the "-e" option so that if there are entries that do not exist yet at least the entries that do exist are executed and the incorrect entries are ignored. Seems like that would be good practice anyway, I've attached a copy of the procps.conf file that I've modifed. I didn't think to keep the originals for diff's and don't want to make incorrect diffs so I just uploaded the file as it is now.