> It only takes a few seconds to grep an NTP source tree for 'STC' (or any > other string. Hardly a difficult task. > > -- > Steve Kostecke <[email protected]> > NTP Public Services Project -http://support.ntp.org/
Grepping is easy. Which source tree shall I download and search? How do I know the server in question isn't running a god awful, ancient SCO fork? Or isn't an appliance? Let us say that I spent more time than I should have on Dr. Mill's site and NTP.org in addition to playing with Google and this newsgroup before posting a question of such minor consequence. Can we put to rest the idea that every "newbie" who posts a question in this group is a feckless boob who in incapable of researching even the simplest nugget of information? Sometimes one senses it's worth going straight to the experts. Honestly, this thread should have died after Martin's first post, but I just can't resist when RTFM is invoked. I wonder how long before we bring Hitler into the fray? NTP(d) is a fantastic tool and I sincerely appreciate all the hard work that goes into it, but it has to be the only "defacto standard" tool I use, commercial or GPL, where it's suggested one should search software code in an attempt to decipher simple diagnostic output. Of course this is a moot point since even if there was a list of all the known refids and their meanings, it would be meaningless since one can fudge the field to be any four letter word (I can think of a few). FWIW, sometimes while pursuing a problem, it's just not possible to ring up the system in question's admin. Corporate politics is a strange beast. I think the best answer I've seen yet is in effect, "I don't know". Fair enough. Thanks, Phreon _______________________________________________ questions mailing list [email protected] https://lists.ntp.org/mailman/listinfo/questions
