starting procps getting invalid argument setting key

[Lars Olesen]

On Ubuntu 12.04, I am not able to update procps with:

<code>
globen:~# apt-get -y --force-yes install --reinstall procps
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages will be upgraded:
  procps
1 upgraded, 0 newly installed, 0 to remove and 111 not upgraded.
Need to get 0 B/225 kB of archives.
After this operation, 0 B of additional disk space will be used.
Reading changelogs... Done
apt-listchanges: Mailing root: apt-listchanges: changelogs for globen.vih.dk
(Reading database ... 49116 files and directories currently installed.)
Preparing to replace procps 1:3.2.8-11ubuntu6 (using .../procps_1%3a3.2.8-11ubuntu6.2_i386.deb) ...
Unpacking replacement procps ...
Processing triggers for ureadahead ...
Processing triggers for man-db ...
Setting up procps (1:3.2.8-11ubuntu6.2) ...
start: Job failed to start
invoke-rc.d: initscript procps, action "start" failed.
dpkg: error processing procps (--configure):
 subprocess installed post-installation script returned error exit status 1
E: Sub-process /usr/bin/dpkg returned an error code (1)
</code>

When trying to start procps, I get:

<code>
globen:~# service procps start
start: Job failed to start
globen:~# tail /var/log/upstart/procps.log
error: "Invalid argument" setting key "kernel.pid_max"
</code>