James, I added back the "env UPSTART_EVENTS=" as manually starting the job complained about this variable to be unknown. With and without the sysctl keys are updated so that looks good on that side.
One thing that I noted in those 2 reboot tests is that my ntpd is exiting after successfully binding on a few interfaces. Could that be related to running procps twice ? Here is an extract of the ntpd error : Dec 6 16:16:53 xeon ntpd[4630]: kernel time sync status 2040 Dec 6 16:16:54 xeon ntpd[4630]: Deleting interface #11 vnet0, fe80::fc54:ff:fe8d:c43c#123, interface stats: received=0, sent=0, dropped=0, active_time=1 secs ... Dec 6 16:16:54 xeon ntpd[4630]: Deleting interface #22 br-vpn0, fe80::6075:82ff:fefa:8a89#123, interface stats: received=0, sent=0, dropped=0, active_time=1 secs Dec 6 16:17:01 xeon CRON[4781]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Dec 6 16:17:03 xeon ntpd[4630]: ntpd exiting on signal 15 Dec 6 16:17:03 xeon ntpdate[4807]: the NTP socket is in use, exiting Dec 6 16:17:03 xeon ntpd[4834]: ntpd 4.2.4p8@1.1612-o Tue Apr 19 07:08:18 UTC 2011 (1) Dec 6 16:17:03 xeon ntpd[4835]: precision = 1.000 usec Dec 6 16:17:03 xeon ntpd[4835]: ntp_io: estimated max descriptors: 1024, initial socket boundary: 16 Dec 6 16:17:03 xeon ntpd[4835]: unable to bind to wildcard socket address 0.0.0.0 - another process may be running - EXITING There always have been a "competition" between ntpd and ntpdate but ntpd was apparently not having a problem before. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/771372 Title: procps runs too early in the boot process To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/771372/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
