X-Spam-Check-By: sourceware.org
Date: Mon, 12 Dec 2005 19:16:55 -0500 (EST)
From: Steve Thompson <smt@vgersoft.com>
Reply-To: smt@vgersoft.com
To: cygwin@cygwin.com
Subject: Re: 'uptime' command producing incorrect uptime
In-Reply-To: <20051212114933.GG17517@calimero.vinschen.de>
Message-ID: <Pine.LNX.4.58.0512121916070.28916@dahlia.vgersoft.com>
References: <439B555A.80803@ineedhosting.net> <Pine.LNX.4.58.0512101742440.16549@dahlia.vgersoft.com>  <20051212114933.GG17517@calimero.vinschen.de>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie.com@cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com

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!

Steve

--
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/