[Bug 50093] Re: Some sysctls are ignored on boot

[Dan Streetman]

Just to reiterate, I'm only marking procps as 'wontfix' because the
sysctl service used in all current releases comes from systemd, *not*
the procps package, so there is nothing to 'fix' in the procps package.

Also, before people get upset, I've only marked this as Wishlist because
the sysctl.d docs clearly explain this is a known issue with clearly
documented ways to work around it. That doesn't mean i don't think this
should be fixed; I absolutely do agree it should be fixed to properly
apply all sysctl settings at boot, including for loadable modules loaded
after boot. That will require upstream systemd work to implement,
however, before backporting into Ubuntu.

-- 
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 sysctls are ignored on boot

Status in procps package in Ubuntu:
  Won't Fix
Status in systemd package in Ubuntu:
  New

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