NESSAholics.com

=> FAQ / Board Issues => Topic started by: vt on September 30, 2004, 08:14:42 pm

Title: the time is wrong
Post by: vt on September 30, 2004, 08:14:42 pm
its two minutes ahead.
Title: Re: the time is wrong
Post by: B on September 30, 2004, 08:23:25 pm
Quote from: "vt"
its two minutes ahead.


You'll never be late!  :D

I noticed it was a few minutes ahead, but never thought to ask about it. LOL.
Title: the time is wrong
Post by: kaysha on September 30, 2004, 08:27:28 pm
fixable... i mentioned it to kelly.  It seems to be almost 5 minutes fast actually.
Title: the time is wrong
Post by: vt on September 30, 2004, 08:29:18 pm
its no biggie, but I was about 5 minutes late to homeroom today.
Title: the time is wrong
Post by: Trolan on September 30, 2004, 08:34:05 pm
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.
Title: the time is wrong
Post by: B on September 30, 2004, 08:34:57 pm
Quote from: "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.


Thanks.

Although now I'll have to get used to the time actually being right, LOL.  :oops:
Title: the time is wrong
Post by: Vultch on September 30, 2004, 08:37:13 pm
now if only Oblivion could be set right. It's 13 minutes fast :razz:
Title: the time is wrong
Post by: kaysha on September 30, 2004, 08:51:02 pm
wtf, asshole.

fixed on oblivion as well.
Title: the time is wrong
Post by: Will on September 30, 2004, 08:51:19 pm
Out of curiousity, why don't you run ntpd?
Title: the time is wrong
Post by: kaysha on September 30, 2004, 08:52:25 pm
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.
Title: the time is wrong
Post by: Will on September 30, 2004, 08:59:36 pm
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.

Quote
    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.