[ntp:questions] Reference Clock driver for getting time via "date" command over telnet?
martin.burnicki at meinberg.de
Thu Apr 22 10:30:50 UTC 2010
Steve Kostecke wrote:
> On 2010-04-21, unruh <unruh at wormhole.physics.ubc.ca> wrote:
>> On 2010-04-21, Movis <ben at internetaddress.com> wrote:
>>> For reasons outside my control, I wish to configure ntpd on Red Hat
>>> to use as the refclock a time obtained by repeatedly telnetting to a
>>> remote machine and using the "date" command.
>>> Could anyone help me put something together which ntpd would accept
>>> as a clock source?
>> Why would they? Noone else in the world would be interested in this.
>> If you are willing to put a few thousand dollars up front, I am sure
>> someone would take it on for you.
> Take a look at http://www.vanheusden.com/time/omnisync/
> OmniSync is a driver for NTPd for people who are firewall-challenged. It
> enables systems to sync time when port 123 (UDP) is blocked. It allows
> you to sync against the daytime service (port 13 tcp/udp), time (port 37
> tcp/udp), SNTS, ICMP, SNMP, precision time protocol (PTP - IEEE 1588),
> (S)NTP via a socks5 proxy server, http and https (both also via proxy
> server). It doesn't directly set the clock but uses NTPd for this as
> this enables you to have multiple time sources as well as bad-chimer
> detection etc.
Hm, AFAIK at least the time and daytime protocols have only 1 second
resolution. Even if there's a way to feed this to ntpd, I doubt ntpd would
accept such jitter, or does it?
More information about the questions