Looks like the previously discussed timelag is manifesting once again. The post timestamps are a couple minutes off from “actual time”.
testing…
About 8 minutes.
And boy is the Board slow. Get the hamster some more meth!
The technical staff has indicated to me that slippage will happen . . . and they’re not going to do anything about it.
your humble TubaDiva
Administrator
Not even the occasional reboot for correction? What happens when it loops itself?
Walls bleeding in the 53rd precinct! Cats and dogs, living together, total hysteria!
Question: How critical is it the the time stamp be exaxtly coordinated to UTC, GMT, etc. as long as posts are in chronological order and the discrepancy is less than an hour or so.
Most difference less than 15 minutes to my notice.
I did say something to Jerry the Tech God about synching up with one of the accepted time signals.
He replied . . . well, for a man with as much knowledge as he has, he must be aware that his suggestion is anatomically impossible. At the very least.
For those of you who are eternally bugged by not being exactly on time, I don’t know what to tell you except you’re going to have to get over it.
your humble TubaDiva
Administrator
Just give it a few more weeks and we can all shift our time zone setting to the east by one.
Or west.
Test Number One
Test Number Two - slow by 19 minutes.
A simple freeware tool such as WebTime will fix this if a Windoze machine. There are similar tools for other platforms, including built-in tools to ping an atomic clock and adjust the time automatically.
You’re right of course. I actually sat there and thought about it and still got it wrong! :smack:
Oh, and apologies for the old-thread bump. I didn’t notice that, either. Arrgh.
Even without some sort of software to synch the clock to some standard, it’s just a ten-second fiddle to correct the time on the server. If the server is running some flavor of Windows, it’s no more difficult than setting the time on your PC - it’s some variant of “Start, Control Panel, Date/Time, plug in the right number, click OK.” If it’s running Netware, IIRC, it’s a simple command-line entry, something like “SET TIME 05:12:00.”
In the absence of synchronizing software, someone might have to perform this terribly onerous job once a week or so, to keep the clock drift from getting out of hand. When I was a sysadmin, I did it every morning during my first cup of coffee. Why the tech staff is telling the admins that this is some big problem that they’re not prepared to deal with is a complete mystery.
It’s not a big problem; just the opposite.
The small tech staff at the Reader has so much to do in the course of a regular day that minor concerns like this are wayyyy down on the list. It’s not meant as disrespect, it’s just that there’s only so much time and so much more to do.
They will get to it as they can, but it’s not up to the second and right on the spot.
your humble TubaDiva
Also: Isn’t the SDMB now hosted on a separate server, outside of the Reader’s offices? It may be that Jerry (upon him be peace) no longer has console-level access to the server, or not easily. In this case, it might be considerably more difficult for him to reset the time, or even impossible.
But if that’s true, why don’t the hosting folks take care of it without our intervention? It would seem to be a simple thing to do with a sync program as a matter of course for all of their servers.
I see my question has been answered [post=5961226]here[/post].