> How does this help get the time from an Oregon Scientific Rugby clock?
> NTP is a protocol for getting the time from another machine - not for
> reading data from the game (or other) port on a PC...
Robin
The NTP daemon needs to get it's time source from somewhere and that
somewhere is a Stratum 0 clock source e.g. a device driver for an MSF
Rugby receiver.
All that needs to be written is a device driver to listen to the line
from the Oregon and return the info as a ascii string in one of the many
forms that NTP recognises. NTP will do the rest, and more.
The source for NTP is largish (1.9M compressed), the executable is not
trival (750K) but it is the "Right Thing" (tm) to provide time sync in
an IP network. It does have many advatages, one you will need with MSF,
if the S0 source is lost NTP freewheels and uses the calculated drift to
maintain good precision in the absence of the S0 source.
p.s. isdst appears to be _set_ by mktime to indicate what the OS believes
the time is.
Are you using a.out or ELF?
The shared libc (ELF) does not break for +ve or -ve values, just sets
isdst to 1.
"mktime" on my box (Slackware 3.x) is _not_ y2k compliant, it breaks if
given 1999 for the year, it uses 99.
--
73 de g1sog
Richard
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Amateur radio callsign: G1SOG Home BBS: G1SOG@GB7SDN.#49.GBR.EU
Amprnet co-ordinator for Wiltshire
My opinions are mine, all mine. None to spare for unopinionated masses.
This message comes from a WinTel free zone. CPU = Cyrix, OS = Linux.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
