I've investigated the issue around the wierd PID value:
There is already a pid file /var/run/dhclient.pid with pid 134519072
This turns out to be an issue with dhclient on hardy. I am not seeing the same thing with jaunty.
Reproducing this:
sudo dhclient badiface0
creates a /var/run/dhclient.pid file of zero length. Then,
sudo dhclient eth0
runs dhclient with reads the empty PID file as 134519072.
This doesn't cause a problem so I'm ignoring it.
I've investigated the issue around the wierd PID value:
There is already a pid file /var/run/ dhclient. pid with pid 134519072
This turns out to be an issue with dhclient on hardy. I am not seeing the same thing with jaunty.
Reproducing this:
sudo dhclient badiface0
creates a /var/run/ dhclient. pid file of zero length. Then,
sudo dhclient eth0
runs dhclient with reads the empty PID file as 134519072.
This doesn't cause a problem so I'm ignoring it.