Mischanko, Edward T wrote:> NTP 4.2.7 has been in development for over 6 months
and
> is very stable, yet, yes, it's still in development.
IIRC over 3 years.
--
E-Mail Sent to this address
will be added to the BlackLists.
___
questions mailing
On 2013-01-27, Garrett Wollman wrote:
> And when it ceases to be "in development" and the FreeBSD net/ntp port
> becomes 4.2.7 instead of 4.2.6, then I will run it.
The next FreeBSD net/ntp "port" will be 4.2.8
http://support.ntp.org/Main/ReleaseNumberingScheme
explains why.
Stable releases ha
"Mischanko, Edward T" writes:
> Garrett,
>
> NTP 4.2.7 has been in development for over 6 months and is very stable,
> yet, yes, it's still in development.
4.2.7 is in a code-freeze pending the release of 4.2.8.
There are <20 small bugs remaining to be fixed, and these issues have
mosly been ar
Garrett,
I didn't realize that my comment would be so offensive to you.
Please accept my apology for trying to be helpful.
Regards,
Ed
> In article <31033FCF05BEE64695655345F1E94EF015FFDD21@BHW-MBX-02>,
> Mischanko, Edward T wrote:
>
> >NTP 4.2.7 has been in development for over 6 months and i
In article <31033FCF05BEE64695655345F1E94EF015FFDD21@BHW-MBX-02>,
Mischanko, Edward T wrote:
>NTP 4.2.7 has been in development for over 6 months and is very stable,
> yet, yes, it's still in development.
And when it ceases to be "in development" and the FreeBSD net/ntp port
becomes 4.2.7 instea
Garrett,
NTP 4.2.7 has been in development for over 6 months and is very stable,
yet, yes, it's still in development.
Regards,
Ed
>
> 2013/1/27, Garrett Wollman :
> > In article
> > ,
> > Michael Tatarinov wrote:
> >>I know only one way.
> >>ntpq -c 'config: leapfile LEAPFILE"
> >
> > That
On 27/01/2013 01:56, Garrett Wollman wrote:
In article ,
Hal Murray wrote:
I suggest submitting a feature request at
https://support.ntp.org/bugs/index.cgi
with a link back to the above bug since it will be the same area of code.
Too many hoops to jump through. Maybe someone who already h
2013/1/27, Garrett Wollman :
> In article
> ,
> Michael Tatarinov wrote:
>>I know only one way.
>>ntpq -c 'config: leapfile LEAPFILE"
>
> That was what I was looking for! In my version of ntpq, at least,
> it's spelled ':config' rather than 'config:', but that did it.
>
> Unfortunately, this sti
In article
,
Michael Tatarinov wrote:
>I know only one way.
>ntpq -c 'config: leapfile LEAPFILE"
That was what I was looking for! In my version of ntpq, at least,
it's spelled ':config' rather than 'config:', but that did it.
Unfortunately, this still doesn't get me anywhere, because the
"pas
I know only one way.
ntpq -c 'config: leapfile LEAPFILE"
2013/1/26, Garrett Wollman :
> I'm using my configuration-management system to distribute a
> leapseconds file for ntpd. After the system installs the new file,
> what does it need to do for ntpd to recognize that the file has
> changed? (
In article ,
Hal Murray wrote:
>I suggest submitting a feature request at
> https://support.ntp.org/bugs/index.cgi
>with a link back to the above bug since it will be the same area of code.
Too many hoops to jump through. Maybe someone who already has an
account at that site can do it.
-GAWol
I know of no way for NTP to know about the new file without restarting NTP
itself. The drift file will allow it to come back into sync very quickly,
so the consequences of a restart should be minimal. NTP reads the leapseconds
file on start-up, I believe.
Regards,
Ed
>
> I'm using my configur
I'm using my configuration-management system to distribute a
leapseconds file for ntpd. After the system installs the new file,
what does it need to do for ntpd to recognize that the file has
changed? (It is obviously undesirable to simply restart a stratum-1
ntpd; I'm looking for the mechanism t
13 matches
Mail list logo
