Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
From: "Philip Aston" <paston@bea.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <15579.35225.764199.450263@bea.com>
Date: Fri, 10 May 2002 09:49:29 +0100
To: cygwin@cygwin.com
Subject: Re: [PATCH] gettimeofday time travels
In-Reply-To: <20020509160449.GF6910@redhat.com>
References: <15547.16136.163472.840007@bea.com>
	<20020415214133.GA19612@redhat.com>
	<15577.12319.622365.566799@bea.com>
	<20020508144104.GA1093@redhat.com>
	<15578.30482.568575.767214@bea.com>
	<20020509160449.GF6910@redhat.com>


Christopher Faylor writes:
 > An NT only solution is not a solution.

I wasn't for a moment suggesting that it was.

 > Syncing every "x" seconds also is not a solution.
 > 
 > The correct solution is to resync after events which cause the clock to
 > stop.

OK, I'll have a crack at this over the weekend following David's
hints.

Looks straightforward. I'll patch the event loop in window.cc to set
some static flag in hires on suspend and/or resume events, and
reinitialise in hires::usecs iff the flag is set.

Let me know if I'm well off track here.

- Phil


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/