1

 

3

 

hmm... i posted that as
1
2
3
see how it's out of order?

 

I have noticed that flood control seems to stop you posting for way longer than 15 seconds sometimes ... but I guess this is something that really only affects us in the Corner, generally

 

ttt

 

I have setup all of the servers using something called ntpd. It's a program which runs and continuously polls time servers (time.apple.com, clock.redhat.com, tick.navy.mil, etc.) and adjusts the clocks of the servers to be synchronous with them. We have 4 separate application servers all running in unison. Your posts come from one of them. If the clocks on those servers are not in harmony a post you make through one could easily show up before a later post made through a different server with a different idea of what time it is. The time of the post is computed on the web server at the time you post.

For some reason the clocks are not in unison, out by as much as 1 minute. I'm going to test and fix the configuration of the clock synchronization to solve this problem now. It should be working but doesn't but it will in a bit once I debug whay the clocks are so far off.

 

Ok, the time sync thing we were doing before wasn't working. I've switched to a less elegant and more reliable method and sync'd all of the servers. Some were off by as much as 100 seconds which would easily explain the ordering and flood control problems.

 

Much oblige, cthree. We thank you for your diligence. Is this a common occurence? For them to go out of sync like that?

 

I wouldn't have thought so since I did "fix" it before so they wouldn't but seeing as how they were as much as 2 minutes different in less than a month I guess it's something to keep an eye on more closely.