Stephen Gutknecht (SAPDB) wrote:
Naturally.You obviously don't work in the same areas I do :) Our serves must be synced to a known references constantly.
On Linux (and I expect other Unixen) the ntpd daemon slows down or speeds up the system clock for a while depending on the error when it got the time from the server, this means that time never goes backwards jumps, unless the clock is many hours out of sync.
I imagine something similar must exist on windows.
http://www.eecis.udel.edu/~ntp/ntp_spool/html/ntpd.html
Eventhough it is clearly possible to keep accurate time and avoid jitter it would be good if sapdb could fail with a little more verbose message or maybe log a warning in stead?
It seems heavyhanded to blow up just because the clock is defective.
--
Regards Flemming Frandsen - http://dion.swamp.dk
PartyTicket.Net co founder & Yet Another Perl Hacker
_______________________________________________
sapdb.general mailing list
[EMAIL PROTECTED]
http://listserv.sap.com/mailman/listinfo/sapdb.general
