On Sun, 15 Mar 2009, Joseph Gwinn wrote:
> In article <qo6dnzljdv8z4cdunz2dnuvz_hwwn...@giganews.com>,
> "Richard B. Gilbert" <rgilber...@comcast.net> wrote:
>
>> Joseph Gwinn wrote:
>>> In article <nbwdnvxq_p-y_idunz2dnuvz_thin...@giganews.com>,
>>> "Richard B. Gilbert" <rgilber...@comcast.net> wrote:
>>>
>>>> Joseph Gwinn wrote:
>>>>> In article <49bd3907.1080...@ntp.org>, ma...@ntp.org (Danny Mayer)
>>>>> wrote:
>>>>>
>>> [snip]
>>>>> 3. The original question was how to interpret a specific status code,
>>>>> 9514. I read the explanation in the documentation, but became no wiser
>>>>> for it. Thus my question.
>>>>>
>>>>> If there isn't a NTP FAQ entry on this, there probably should be. Our
>>>>> sysadmins were flummoxed by the cloud of 5914 codes, and they are far
>>>>> too busy to undertake a research project. (The deeper problem is that
>>>>> some managers believe that NTP is plug and play, which isn't quite true.)
>>>>>
>>>>>
>>>>> The various answers and questions I've gotten have been quite useful, as
>>>>> they give me a list of things to think about and investigate, things I
>>>>> might not have thought of, or soon thought of.
>>>>>
>>>>> Joe Gwinn
>>>> Joe,
>>>>
>>>> You need to proofread your message text a little more carefully!!
>>>>
>>>> Which error are you ACTUALLY getting? You say 9514 and then 5914!
>>>> Which is it?
>>>
>>> You're right, but it wouldn't help, for an odd reason.
>>>
>>> The status code is 9514.
>>>
>>> But I have a Clausing 5914 lathe.
>>>
>>> Inherent dyslexia inducer.
>>>
>>>
>>>> Also, you might try Google with the FULL and EXACT text of the error
>>>> message!
>>>
>>> It's "9514", pulled from a field in peerstats records. Think I'll get
>>> many false hits? Qualifying 9514 with peerstats brought me back to this
>>> thread.
>>>
>>> So, tried "Maximum Distance Exceded", got led back to this exact news
>>> thread.
>>>
>>> But let's say I did find some relevant hits. This is the Internet. How
>>> would I know which hits to believe?
>>>
>>
>> I would be influenced by who wrote it and who disagreed with him!
>
> But what if I listen to the loudest one?
>
>
>>> The FAQ has to be the place for such explanations.
>>
>> I'm not sure if this qualifies as an FAQ as I don't recall that it has
>> come up before. FAQ stands for Frequently Asked Questions.
>
> RAQ then? Rarely Asked Questions
>
> Seriously, I can't believe that I'm the only person in history to be
> perplexed by these status codes, and those little three-word summaries
> are a bit telegraphic.
You have lots of company, sadly. A decoder function would
be 'Good'. There are obstacles to this, as remarked by
others, and a serious lack of volunteer time to code a
solution. No one will stop you, if you wish to contribute....
In the current build I find the TEST status codes in
ntp.h. They have changed, from release to release, so
consult your source for particulars.
There has been considerable improvement in NTP from
V3 to V4. You should consider upgrading, it really
is better.
>
> Joe Gwinn
>
> _______________________________________________
> questions mailing list
> questions@lists.ntp.org
> https://lists.ntp.org/mailman/listinfo/questions
>
_______________________________________________
questions mailing list
questions@lists.ntp.org
https://lists.ntp.org/mailman/listinfo/questions
