home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!stanford.edu!agate!dog.ee.lbl.gov!lbl.gov!vxwexplo
- From: Bob Herlien <hebo@mbari.org>
- Newsgroups: comp.os.vxworks
- Subject: re: comp.os.vxworks newsdigest
- Date: Fri, 20 Nov 92 8:28:17 PST
- Organization: Lawrence Berkeley Laboratory, Berkeley CA
- Lines: 33
- Sender: vxwexplo@lbl.gov
- Message-ID: <9211201627.AA19991@nettlerash.berkeley.edu>
- NNTP-Posting-Host: 128.3.112.16
- Originator: daemon@vxw.ee.lbl.gov
-
- >
- > Newsgroups: comp.os.vxworks
- > Subject: Setting time on VxWorks board with NTP
- > Date: 19 Nov 1992 17:55:44 GMT
- > From: nicinski@fndaud.fnal.gov (Tom Nicinski)
- > Organization: Fermi National Accelerator Laboratory, Batavia IL
- > Keywords: NTP
- > Message-ID: <1egkf0INNs75@fnnews.fnal.gov>
- >
- >
- > I'd like to set the time on a VxWorks board when ntpd is started. I'm using
- . . .
- > If I set the time by hand (or other means) with setgmt, it takes NTP quite
- > a while to say that the 4 second (as an example) offset should be corrected
- > with one big correction. This also is unaccepatable, since the VxWorks
- >
-
- Yes, initialization is a problem with NTP. As it stands, it takes NTP
- quite a few minutes (I think it's around 6 to 8) to decide that your time
- is too far off, so it needs to reset the time. There are a couple of potential
- solutions to to this: 1) port ntpdate, and include its functionality at
- initialization time, or 2) port NTP version 3, and tune it at initialization
- to slew very fast. I've been off on other parts of our project, and haven't
- devoted any time at all to NTP. Eventually, I expect I'll need to do one
- of the above.
-
- BTW, I'll be out of town until Nov 30, so if you want to discuss it, send
- some email after then.
-
- --------------------------------------------------------------
- Bob Herlien
- MBARI (Monterey Bay Aquarium Research Institute)
- hebo@mbari.org
-