-------- In message <[email protected]>, =?iso-8859-1?Q?=22Bj=F6rn_Gabrielsson=22?= writes:
>Nevertheless I was a bit surprised that the computer continued to serve >time claiming to be a S1-server, even if both local refclock and a number >of external S1-servers said time was false. I dont know if recent ntpd and >operating system versions still have this problem. Yeah, this is the kind of shit you have to put up with when your time-server source code is 100+ KLOC and has gotten to that size by "lets just add this feature" methodologies. >Poul-Henning, for the updated server with local refclock, have you >elaborated over My first target is a daemon for clients, that's the most efficient way to eliminate as many KLOC-executions from the world as possible as fast as possible. After that, the intent is to reuse the same components also for S2+ slave servers, and later again S1 servers. But the target right here and now is clients only. -- 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.
