I think the issues are less with the actual initial setting of the clock, and more with the constant adjustment of the clock that being an SNTP client implies. Some could always be wondering if their clock might be adjust backward by some small amount, but enough to make a database update log entry occur in the wrong sequence, thus invalidating rollback processes. This could, possibly, be alleviated somewhat by doing adjustments once per day, and preventing updates from happening during the adjustment period?
Tim Hare Senior Systems Programmer Florida Department of Transportation (850) 414-4209 ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
