'uptime' command producing incorrect uptime

Steve Thompson smt@vgersoft.com
Tue Dec 13 00:16:00 GMT 2005

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 after being up for 66 days.
> It's using GetTickCount only if neither GetSystemTimes, nor
> NtQuerySystemInformation is available, which is on Win9x.
> NT systems shouldn't be affected by this.

Yes, of course you're right. No danger of 9x being up for that long!


Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

More information about the Cygwin mailing list