David Woolley wrote: > Danny Mayer wrote: >> David Woolley wrote: >> >>> Once you have an NTP client, as against an SNTP one, writing a server is >>> a relatively trivial exercise. >> That makes no sense. There is no such think as just an NTP client. An >> NTP client is both a client and a server. > > That makes no sense. My point is that, in practice, that is the case, > so if he has third party code for a client, one would think he would > have code for a server, already. However, it is fairly trivial to cut > out the server code from the reference implementation and still have a > working client. Simply ignoring client and symmetric packets will > effectively disable the server function in ntpd. > > It's not clear whether his client is one he is written, whether it is > actually in C#, and even whether it is really an NTP client at all. > It's possible that he has some third party SNTP client code. Also, > English obviously isn't his first language, which means you have to be > careful not to assume that the literal interpretation is the only > possible intended one. >
I know of no implementation which could be considered an NTP client only, just NTP implementations that are both client and server. There are, however, plenty of SNTP clients. Danny _______________________________________________ questions mailing list questions@lists.ntp.org https://lists.ntp.org/mailman/listinfo/questions
