On Mon, Aug 11, 2008 at 12:58:54PM +1000, Paul Szabo wrote: > Running the commands suggested, I get: That's interesting, but its looking like its not a procps bug. Or perhaps there is something procps assumes that is incorrect.
There is no overflow problems here, the manual calculation is agreeing with procps > PID START CMD > 24954 12:48 bash and > [EMAIL PROTECTED]:~$ echo '1218423322 - 2339691.29 + ( 233925387 /100 )' | > bc | perl -e 'use Time::localtime; my $mytime=<>; ; print > ctime($mytime)."\n";' > Mon Aug 11 12:48:03 2008 Looking at the values: The now() time is correct. The uptime is about 29 days, the computer was booted 11am 15th July Now you would expect that the uptime and the process start time would be pretty close to each other, because they are being done at the same time, or a second or so between them. But they are not: In fact, your process start time is *less* than the uptime, by about 438 seconds, or 7 minutes. > Mon Aug 11 12:55:15 EST 2008 > Mon Aug 11 12:48:03 2008 That's 7 minutes. So, the kernel is giving the wrong start time. -- Craig Small GnuPG:1C1B D893 1418 2AF4 45EE 95CB C76C E5AC 12CA DFA5 http://www.enc.com.au/ csmall at : enc.com.au http://www.debian.org/ Debian GNU/Linux, software should be Free -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
