-------- In message <0AA8645271A94DF3968C90FE6BF94276@Alta>, "David J Taylor" writes:
>- that there is (eventually) a Windows implementation. I'm writing the code to be as portable as I can make it, but I have neither Windows machines nor clue how to program for their kernel-time-api. >- that it responds to "ntpq -pn" and "ntpq -crv" commands so that it can be >easily remotely monitored. The jury is still out on the control protocol. To be honest I don't much like it from a security point of view, and the parameters of my clock control algorithm may not map well into its datafields. Time will show... -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [email protected] | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. _______________________________________________ time-nuts mailing list -- [email protected] To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there.
