I've noticed that the time on the AAC server seems to be creeping slowly ahead.
While being ahead of your time is sometimes good, this could cause some real problems down the road when it's eventually corrected; ie: out-of-order replies to posts as we observed a few months ago.
As it is, to reduce the out-of-order situation, I suggest that the clock be gradually corrected over several days, perhaps re-setting the clock by 10 minute increments during slow periods, so that there will be a minimum of out-of-order posts.
I suggest that whomever is maintaining the server should have a look at the FAQ on the NIST site about how to synchronize server clocks with NIST.
http://tf.nist.gov/service/its.htm
I've done this with my computers; it's very easy to do with Win XP Pro. YMMV.
While being ahead of your time is sometimes good, this could cause some real problems down the road when it's eventually corrected; ie: out-of-order replies to posts as we observed a few months ago.
As it is, to reduce the out-of-order situation, I suggest that the clock be gradually corrected over several days, perhaps re-setting the clock by 10 minute increments during slow periods, so that there will be a minimum of out-of-order posts.
I suggest that whomever is maintaining the server should have a look at the FAQ on the NIST site about how to synchronize server clocks with NIST.
http://tf.nist.gov/service/its.htm
I've done this with my computers; it's very easy to do with Win XP Pro. YMMV.
Last edited: