[Bug 50093] Re: Some sysctl's are ignored on boot

[Brian Martin]

*** 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
Foundations Bugs, which is subscribed to procps in Ubuntu.
https://bugs.launchpad.net/bugs/50093

Title:
  Some sysctl's are ignored on boot

Status in procps package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: procps

  /etc/init.d/procps.sh comes too early in the boot process to apply a
  lot of sysctl's. As it runs before networking modules are loaded and
  filesystems are mounted, there are quite a lot of commonly-used
  sysctl's which are simply ignored on boot and produce errors to the
  console.

  Simply renaming the symlink from S17 to > S40 probably isn't a great
  solution, as there are probably folk who want and expect some sysctl's
  to be applied before filesystems are mounted and so on. However,
  simply ugnoring something as important as sysctl settings isn't really
  on. Administrators expect the settings in /etc/sysctl.conf to take
  effect.

  One sto-gap solution would be to run sysctl -p twice; once at S17 and once at S41. There may still be some warnings and errors, but everything would be applied. A different, more complex approach might be to re-architect the sysctl configuration into something like;
   
      /etc/sysctl.d/$modulename

  and have the userland module-loading binaries take care of applying
  them after modules are loaded. Though this may take care of explicitly
  loaded modules only, I'm not sure.

  Incidentally, /etc/sysctl.conf still refers to
  /etc/networking/options, but hasn't that been deprecated?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/procps/+bug/50093/+subscriptions