Re: 'uptime' command producing incorrect uptime

2005-12-12 Thread Steve Thompson
On Mon, 12 Dec 2005, Corinna Vinschen wrote: > On Dec 10 17:50, Steve Thompson wrote: > > It also appears to > > be wrong for uniprocessor hosts that have been up for more than 49.7 days > > because of the 32-bit value returned by GetTickCount(); my own system > > reported an uptime of 16 days af

Re: 'uptime' command producing incorrect uptime

2005-12-12 Thread Corinna Vinschen
On Dec 10 22:23, Jack wrote: > Hi there, > > It appears to me that the uptime command is not producing the correct > uptime and, in fact, is running twice as fast as it should be. > > [EMAIL PROTECTED] ~ > $ uptime > 22:03:00 up 98 days, 13:37, 1 user, load average: 0.00, 0.00, 0.00 > > [EMAI

Re: 'uptime' command producing incorrect uptime

2005-12-12 Thread Corinna Vinschen
On Dec 10 17:50, Steve Thompson wrote: > It also appears to > be wrong for uniprocessor hosts that have been up for more than 49.7 days > because of the 32-bit value returned by GetTickCount(); my own system > reported an uptime of 16 days after being up for 66 days. It's using GetTickCount only

Re: 'uptime' command producing incorrect uptime

2005-12-10 Thread Steve Thompson
On Sat, 10 Dec 2005, Jack wrote: > It appears to me that the uptime command is not producing the correct > uptime and, in fact, is running twice as fast as it should be. > [...] I've noticed a similar effect recently, and looked in the sources. If you take a look at the algorithm used by cygwin (