From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-0.9 required=5.0 tests=BAYES_00,FORGED_GMAIL_RCVD, FREEMAIL_FROM autolearn=no autolearn_force=no version=3.4.4 X-Google-Thread: 103376,30bb735cf84485f7 X-Google-Attributes: gid103376,domainid0,public,usenet X-Google-Language: ENGLISH,ASCII-7-bit Path: g2news1.google.com!postnews.google.com!b64g2000hsa.googlegroups.com!not-for-mail From: george.priv@gmail.com Newsgroups: comp.lang.ada Subject: Re: delay until problem in Windows Date: Mon, 7 Apr 2008 07:51:30 -0700 (PDT) Organization: http://groups.google.com Message-ID: <3de09801-9dab-4dd8-a5e4-2aa7017628fe@b64g2000hsa.googlegroups.com> References: <9bfa59b1-c5ef-42ee-9d2a-729d215293a3@a1g2000hsb.googlegroups.com> <72ac7dad-927e-4254-98de-2b6429ae1261@b1g2000hsg.googlegroups.com> NNTP-Posting-Host: 151.196.71.114 Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Trace: posting.google.com 1207579890 28334 127.0.0.1 (7 Apr 2008 14:51:30 GMT) X-Complaints-To: groups-abuse@google.com NNTP-Posting-Date: Mon, 7 Apr 2008 14:51:30 +0000 (UTC) Complaints-To: groups-abuse@google.com Injection-Info: b64g2000hsa.googlegroups.com; posting-host=151.196.71.114; posting-account=VnNb3AoAAACTpRtCcTrcjmPX7cs92k1Q User-Agent: G2/1.0 X-HTTP-Via: 1.1 SPARKS X-HTTP-UserAgent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.13) Gecko/20080311 Firefox/2.0.0.13,gzip(gfe),gzip(gfe) Xref: g2news1.google.com comp.lang.ada:20863 Date: 2008-04-07T07:51:30-07:00 List-Id: On Apr 7, 10:43 am, george.p...@gmail.com wrote: > On Apr 7, 3:25 am, "Dmitry A. Kazakov" > wrote: > > > On Sun, 6 Apr 2008 20:10:38 -0700 (PDT), george.p...@gmail.com wrote: > > > On Apr 5, 6:51 pm, george.p...@gmail.com wrote: > > > [...] > > > > with Ada.Calendar; > > > use Ada.Calendar; > > > I don't know the implementation of, but Ada.Calendar is a political time, > > influenced by the time synchronization stuff. What happens if you replace > > it by Ada.Real_Time? > > > -- > > Regards, > > Dmitry A. Kazakovhttp://www.dmitry-kazakov.de > > It may worth trying and I will set this up running at first > opportunity, but I think since it is a particular computer system/OS > combination it should eliminate "political" issue since all systems > are in one time zone and all synced from the same time server. So far > I saw that happening only on one system with Server 2003. Similar > hardware running Debian is doing fine. Other machines running Windows > XP and Vista (Notebook) went for 32 hours now and doing fine. All > workstations at my place are the same - that limits my sample pool. I > also do repeat run on failed machine to see if there will be > consistency in times. > > Regards, > > George Privalov As soon as I posted that message, my XP workstation failed. But time is now off forward 2 seconds after 30.5 hours. So drama is not over yet. Actual Delay: 10.000123715, Running (h): 30.430967673 Actual Delay: 10.000125595, Running (h): 30.433745487 Actual Delay: 10.000125257, Running (h): 30.436523299 Actual Delay: 10.000124860, Running (h): 30.439301112 Actual Delay: 10.000124743, Running (h): 30.442078925 Actual Delay: 12.000310334, Running (h): 30.445412345 Actual Delay: 12.000189837, Running (h): 30.448745732 Actual Delay: 12.000190605, Running (h): 30.452079118 Actual Delay: 12.000190805, Running (h): 30.455412505 Actual Delay: 12.000191032, Running (h): 30.458745892 Actual Delay: 12.000189268, Running (h): 30.462079278 Actual Delay: 12.000190642, Running (h): 30.465412665 Actual Delay: 12.000190666, Running (h): 30.468746051 Actual Delay: 12.000190224, Running (h): 30.472079438 Actual Delay: 12.000190730, Running (h): 30.475412825 George