Pascal Obry wrote:
>This is expected as the Calendar.Clock can be adjusted for many reasons. >Like a DST change, an NTP synchronization or a user change in on the >system. Furthermore, GNAT clock implementation is based on a performance >counter (this gives a high resolution clock) and needs slight adjustment >from time to time. The problem you are reporting is probably due to one >of those adjustments.
As i see in windows time synchronization settings, the time adjustment happenes every week, but "delay until" duration increasing happenes every 10 hours,
and remain increased forever.
More over the adjustment could broke one "delay until", but i see increased every delay until after 10 hours working.
>The "delay until" construct is based on the monotonic clock
>(Ada.Realtime.Clock). Using this clock you should not have the above >problem. This is really the clock to used for long lived applications.
>Can you confirm that using the Ada.Realtime.Clock fixes the problem ?
I'll test it and notify you.