the time is wrong

[vt]

its two minutes ahead.

[B]

its two minutes ahead.

You'll never be late!  

I noticed it was a few minutes ahead, but never thought to ask about it. LOL.

[kaysha]

fixable... i mentioned it to kelly.  It seems to be almost 5 minutes fast actually.

[vt]

its no biggie, but I was about 5 minutes late to homeroom today.

[Trolan]

Ok, time resynced.  Not sure why it diverged, but it'll be dead on from now on, as it'll resync to the GPS clock every day.

[B]

Ok, time resynced.  Not sure why it diverged, but it'll be dead on from now on, as it'll resync to the GPS clock every day.

Thanks.

Although now I'll have to get used to the time actually being right, LOL.  :oops:

[Vultch]

now if only Oblivion could be set right. It's 13 minutes fast :razz:

[kaysha]

wtf, asshole.

fixed on oblivion as well.

[Will]

Out of curiousity, why don't you run ntpd?

[kaysha]

that is what was running on shell and oblivion that got the clocks out of sync.

now we switched to just using ntpdate update once a day.

[Will]

Weird. ntpd works like a charm on khristine (home FBSD machine).

Reason why I was asking is that the ntpdate man page kinda discourages such use.

    The ntpdate utility can be run manually as necessary to set the host
     clock, or it can be run from the host startup script to set the clock at
     boot time.  This is useful in some cases to set the clock initially
     before starting the NTP daemon ntpd(8).  It is also possible to run
     ntpdate from a cron(8) script.  However, it is important to note that
     ntpdate with contrived cron(8) scripts is no substitute for the NTP dae-
     mon, which uses sophisticated algorithms to maximize accuracy and relia-
     bility while minimizing resource use.  Finally, since ntpdate does not
     discipline the host clock frequency as does ntpd(8), the accuracy using
     ntpdate is limited.

But you probably knew that already.