Forum Home
PC World Chat
 
Thread ID: 81130 2007-07-17 12:06:00 Yet another thread about the forum clock... Erayd (23) PC World Chat
Post ID Timestamp Content User
569757 2007-07-18 04:04:00 Who does it affect to the extent that it really matters. Transactions here aren't on the futures market or the sharemarket, where someone's automated bidding system has to bid at the correct time to the last millisecond in order to profit.

As long as it's within a day or so, why worry?

I think I've suggested before that a webcamera pointed at a sundial would do.
Graham L (2)
569758 2007-07-18 04:28:00 Who does it affect to the extent that it really matters. Transactions here aren't on the futures market or the sharemarket, where someone's automated bidding system has to bid at the correct time to the last millisecond in order to profit.

As long as it's within a day or so, why worry?

I think I've suggested before that a webcamera pointed at a sundial would do.

Think updates, network time, unix time stamps, database connections, apache httpd processes etc. Weird things happen when a clock is out of sync.
vinref (6194)
569759 2007-07-18 05:19:00 great news everyone!

Even though we really do enjoy having everybody aggravated by the wrong time in the forums (honestly, we love it), I've notified our server person about the problem.

He'll have a looksie soon, and we'll keep you updated.

Until then, please continue to be annoyed and confused at the wrong time. Turn up late for work and blame us instead :)
Jan Birkeland (4741)
569760 2007-07-18 06:22:00 ...Weird things happen when a clock is out of sync.The only "weird things" which happen here when the clock is slow are some members' knickers twisting tighter and tighter. :lol: The screams are delightful.

Get the "server person" to use random times, or change the timezone once a week. Jan.:thumbs:
Graham L (2)
569761 2007-07-18 06:27:00 Lol, I don't even look at the time stamps on the posts, just the date. Its ironical however that like clockwork, someone starts one of these threads up ever so often. beeswax34 (63)
569762 2007-07-18 06:27:00 The only "weird things" which happen here when the clock is slow are some members' knickers twisting tighter and tighter. :lol: The screams are delightful.

Trust me. I once ran Apache and Drupal on a box with a dodgy bios battery and the time kept resetting. Edits and updates went missing all the time and refreshes were very slow. Software upgrades were completely stuffed. The bios battery is still dodgy, but I keep time with ntpd and all is OK now.
vinref (6194)
569763 2007-07-18 06:42:00 Trust me. I have seen the clock on this forum drop behind "real time" a number of times. Guess what? The only problem is the people who seem to think that it really matters on this forum. :D

A "dodgy bios battery" affects the system clock only when the computer is rebooted.

Between boots, or manual or automatic time settings, the time is maintained by a system "tick" interrupt.

Almost all computers before the IBM PCAT of 1982, didn't have battery powered clocks. Even large mainframes needed the date and time entered by the operator when the system was powered up. Sometimes the operator would get it wrong. ;) That sometimes mattered. In many systems, it didn't matter. Many people with mini computers or Apple IIs or IIIs, or IBM PCs didn't ever set the date or time.
Graham L (2)
569764 2007-07-18 06:47:00 Trust me . I have seen the clock on this forum drop behind "real time" a number of times . Guess what? The only problem is the people who seem to think that it really matters on this forum . :D

A "dodgy bios battery" affects the system clock only when the computer is rebooted .

Between boots, or manual or automatic time settings, the time is maintained by a system "tick" interrupt .

Almost all computers before the IBM PCAT of 1982, didn't have battery powered clocks . Even large mainframes needed the date and time entered by the operator when the system was powered up . Sometimes the operator would get it wrong . ;) That sometimes mattered . In many systems, it didn't matter . Many people with mini computers or Apple IIs or IIIs, or IBM PCs didn't ever set the date or time .

You're weird Graham . You may need to readjust your clock!

And no, we are not discussing reboots or IBM PCATs or whatever you last used .

And thanks to Jan for finally taking this up . I await to see if anything has changed, especially with refreshes .
vinref (6194)
569765 2007-07-18 06:55:00 I see that the clock is 5:46 p . m . and my watch says it's a bit after 6 p . m . So what? The forum is running . It hasn't fallen over . It works .

We weren't discussing your box with a dodgy bios battery . I'd have replaced the cell . Losing bios settings is potentially more of a problem than a flakey time .

On systems where the time mattered, we installed independent clock cards . My practice was to turn off the OS clock interrupt and fetch time information from the external clock when it was wanted . (That was because the time interrupt used about 2% of the CPU time on all systems I measured this, and we always needed all the CPU) .

Untwist your knickers, vinref . You'll be more comfortable .
Graham L (2)
569766 2007-07-18 06:58:00 I see that the clock is 5:46 p . m . and my watch says it's a bit after 6 p . m . So what? The forum is running . It hasn't fallen over . It works .

We weren't discussing your box with a dodgy bios battery . I'd have replaced the cell . Losing bios settings is potentially more of a problem than a flakey time .

On systems where the time mattered, we installed independent clock cards . My practice was to turn off the OS clock interrupt and fetch time information from the external clock when it was wanted . (That was because the time interrupt used about 2% of the CPU time on all systems I measured this, and we always needed all the CPU) .

Untwist your knickers, vinref . You'll be more comfortable .

Calm down Graham .
vinref (6194)
1 2 3 4 5