Forum clock

Andon · Post by **Andon** » Sat Nov 27, 2010 2:32 am

Nah, someone put the server in a centrifuge and, since it's going faster, we have the time dilation effect.

Post by **FreeBeer** » Sat Nov 27, 2010 2:48 am

Centrifuge, eh? Well, Toronto does think it is the centre of the universe.

fuzzylunkin1 · Post by **fuzzylunkin1** » Sat Nov 27, 2010 12:38 pm

Errr, does the forum not use the system clock?

Or does the system clock not update with a time server as often as it should??

Post by **Tigereye** » Sat Nov 27, 2010 6:50 pm

When the forum's OS was using the system clock (BIOS clock), it was falling behind slowly (as you guys noticed before).
It was thought that the BIOS was for some reason going slow, so the OS was reconfigured to keep its own time instead of syncing with the BIOS time.

Fast forward to today, and it's clear that the OS's clock is now slightly fast; we have the opposite problem.

It's simple to add a cronjob to sync with NTP every ${interval} but that is like taking a tylenol for a headache. Yeah it'll cure the symptom but the underlying problem will still exist. The cronjob isn't added (so our server isn't syncing *automatically* with a time source) until we can figure out why we're drifting ever so slowly.

It's smarter to solve the problem rather than apply bandaids.
"do it right the first time, or do it right the next time after having wasted time doing it wrong"

--TE

fuzzylunkin1 · Post by **fuzzylunkin1** » Sat Nov 27, 2010 9:56 pm

The problem is there because it's not hooked up to a $#@!ing atomic clock.

Post by **pkk** » Sat Nov 27, 2010 10:30 pm

fuzzylunkin1 wrote:QUOTE (fuzzylunkin1 @ Nov 27 2010, 10:56 PM) The problem is there because it's not hooked up to a $#@!ing atomic clock.

No, there is a hardware problem. Clock shouldn't go that wrong. There should be only a second or less if you sync once a week.

fuzzylunkin1 · Post by **fuzzylunkin1** » Sun Nov 28, 2010 2:29 am

pkk wrote:QUOTE (pkk @ Nov 27 2010, 05:30 PM) There should be only a second or less if you sync once a week.

I know. Apparently it's not being synced very often.

Here's an idea, Mr. Admin. Add a cron-job to vixie-cron (or whatever you decided to use) to sync with your favorite network time server once or twice a week and figure out the problem between the time you're working, doing whatever else you do around here, having a real life, and, god-forbid, $#@!ing your wife. Hell, have a bash script record the time at key moments automatically if you think knowing the amount of time it's off might help.

Post by **Tigereye** » Sun Nov 28, 2010 6:39 am

Band-aid administration leads to more bandaids and increased complexity of maintenance.

I'm going to continue looking for a solution to the problem instead of alleviating the symptoms. I've already investigated some solutions to this "problem" and am ready to employ the one that fits best. I just need to collect a bit more data.

This really isn't a big deal though... unless you're OCD like the OP

--TE

madpeople · Post by **madpeople** » Sun Nov 28, 2010 1:18 pm

Tigereye wrote:QUOTE (Tigereye @ Nov 27 2010, 06:50 PM) the BIOS was for some reason going slow, the OS's clock is now slightly fast

Just use the average of the two?

Cadillac · Post by **Cadillac** » Sun Nov 28, 2010 4:45 pm

Tigereye wrote:QUOTE (Tigereye @ Nov 28 2010, 06:39 AM) Band-aid administration leads to more bandaids and increased complexity of maintenance.

I'm going to continue looking for a solution to the problem instead of alleviating the symptoms. I've already investigated some solutions to this "problem" and am ready to employ the one that fits best. I just need to collect a bit more data.

This really isn't a big deal though... unless you're OCD like the OP

--TE

TIME is not to be trifled with!