On Apr 7, 3:25 am, "Dmitry A. Kazakov" <mail...@[EMAIL PROTECTED]
>
wrote:
> On Sun, 6 Apr 2008 20:10:38 -0700 (PDT), george.p...@[EMAIL PROTECTED]
wrote:
> > On Apr 5, 6:51 pm, george.p...@[EMAIL PROTECTED]
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
op****tunity, 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
|
