[ntp:questions] Re: [Patch] refclock_palisade was "Unexpected offset on startum 1 server"

David L. Mills mills at udel.edu
Sat Jun 11 21:15:35 UTC 2005


I haven't heard from Sven Dietrich, the original maintainer, for some 
time. As in many such things the enthusiasm may decline when the 
employer or job description changes. Frankly, I don't think we need a 
maintainer for every clock. The Palisade driver was built in 1997 and 
last changed, probably updated by me for some interface wiggle, in 2003.

It's tough to know when to expire a clock. Very old ones that haven't 
been heard for awhile have a nasty habit of showing up, like the msfees 
and heath and tpro. Others like the bancomm and leitch are still in use 
at national laboratories who have not volunteered to maintain.

What I would like to see is for the "old" interface to expire and be 
weeded from the code base. Right now both the old and new (ntp_refclock) 
  interfaces are supported and there are a handful of drivers that have 
not been converted.


Bjorn Gabrielsson wrote:
> While not ready for maintainership, I am quite happy to help with
> testing. What made Trimble stand down on maintainership? They still
> market the Syncronization Kit for NTP use...
> --
>         Björn
> "David L. Mills" <mills at udel.edu> writes:
>>There are quite a number of Palisade clocks in circulation; I have one
>>here that I occasionally fire up. While I don't volunteer to be an
>>official maintainer, the driver will remain indefinately in the
>>distribution that leaves here.
>>Harlan Stenn wrote:
>>>Fabien and Lionel,
>>>The Palisade refclock has no maintainer and will be deprecated unless
>>>a maintainer is found.
>>>Do you know anybody who would like to volunteer to be the maintainer
>>>for the Palisade refclock?

More information about the questions mailing list