On Wed, Dec 30, 2015 at 04:50:45AM -0800, Colin Percival wrote:
> So... is someone going to be keeping this file up to date? We seem to have
> the same information in contrib/tzdata/leapseconds (which is being kept up
> to date -- thank you edwin and delphij!) but having this file in /etc/ntp/
>
On Wed, 2015-12-30 at 04:50 -0800, Colin Percival wrote:
> On 10/16/15 07:04, Cy Schubert wrote:
> > Add default leap-seconds file. This should help ntp networks get
> > the
> > leap second date correct
> >
> > Added:
> > head/etc/ntp/
> > head/etc/ntp/Makefile (contents, props
In message <1451491490.1369.41.ca...@freebsd.org>, Ian Lepore writes:
> On Wed, 2015-12-30 at 04:50 -0800, Colin Percival wrote:
> > On 10/16/15 07:04, Cy Schubert wrote:
> > > Add default leap-seconds file. This should help ntp networks get
> > > the
> > > leap second date correct
> > >
>
On 10/16/15 07:04, Cy Schubert wrote:
> Add default leap-seconds file. This should help ntp networks get the
> leap second date correct
>
> Added:
> head/etc/ntp/
> head/etc/ntp/Makefile (contents, props changed)
> head/etc/ntp/leap-seconds (contents, props changed)
So... is
We already have an example to work from. The family of ports (ntp,
ntp-devel) installs ${LOCALBASE}/sbin/update-leap. It would be fine except
for the fact that it's written in Perl, not something we'd want to visit on
FreeBSD again. I'm sure it could be rewritten in shell script or C/C++.
--
On Sat, 2015-10-17 at 22:20 +0100, David Malone wrote:
> On Sat, Oct 17, 2015 at 12:25:50PM -0600, Ian Lepore wrote:
> > If the leapseconds file is present, the leap bits for reference
> > clocks and downstratum servers are ignored.
> >
> > I can't determine from casual code examination
On Sat, Oct 17, 2015 at 05:48:19PM -0600, Warner Losh wrote:
> It should be very easy to try to fetch it once a day in June and December
> until you succeed from each of the URLs in a list, with the default
> list being the two canonical (for the US at least) sources. Shouldn’t
> be more than a
Hi Warner,
I was trying to check Ian's specific concern, that a valid source
of leap seconds might be ignored if a expired leapseconds file was
present. It seems that this is not the case, at lease based on my
reading of the code and comments. I included the references to the
code, so others
> On Oct 17, 2015, at 3:20 PM, David Malone wrote:
>
> On Sat, Oct 17, 2015 at 12:25:50PM -0600, Ian Lepore wrote:
>>If the leapseconds file is present, the leap bits for reference
>>clocks and downstratum servers are ignored.
>>
>> I can't determine from casual
In message <00150ef2-0020-42e5-a1e5-324a23975...@bsdimp.com>, Warner Losh
writes:
> > On Oct 17, 2015, at 3:20 PM, David Malone =
> wrote:
> >=20
> > On Sat, Oct 17, 2015 at 12:25:50PM -0600, Ian Lepore wrote:
> >>If the leapseconds file is present, the leap bits for
Agreed, this would be best. There was a suggestion a GSoC person could do
it (though I'm willing to roll up my sleeves if necessary).
--
Cheers,
Cy Schubert or
FreeBSD UNIX: Web: http://www.FreeBSD.org
The
> On Oct 17, 2015, at 1:25 PM, Ian Lepore wrote:
>
> On Sat, 2015-10-17 at 13:19 -0600, Warner Losh wrote:
>> Until the next leap second…. It would be better to just
>> always try to grab the latest one… Can we put something
>> in periodic to do that so users that have
In message <1445109956.71631.44.ca...@freebsd.org>, Ian Lepore writes:
> On Sat, 2015-10-17 at 13:19 -0600, Warner Losh wrote:
> > Until the next leap secondÂ
. It would be better to just
> > always try to grab the latest oneÂ
Can we put something
> > in periodic to do that so users that have
On Fri, 2015-10-16 at 14:04 +, Cy Schubert wrote:
> Author: cy
> Date: Fri Oct 16 14:04:16 2015
> New Revision: 289421
> URL: https://svnweb.freebsd.org/changeset/base/289421
>
> Log:
> Add default leap-seconds file. This should help ntp networks get
> the
> leap second date correct
>
On 10/17/15 11:25 AM, Ian Lepore wrote:
> On Fri, 2015-10-16 at 14:04 +, Cy Schubert wrote:
>> Author: cy
>> Date: Fri Oct 16 14:04:16 2015
>> New Revision: 289421
>> URL: https://svnweb.freebsd.org/changeset/base/289421
>>
>> Log:
>> Add default leap-seconds file. This should help ntp
Until the next leap second…. It would be better to just
always try to grab the latest one… Can we put something
in periodic to do that so users that have releases
that are older than 6 months aren’t screwed?
Warner
> On Oct 16, 2015, at 8:04 AM, Cy Schubert wrote:
>
> Author:
> On Oct 17, 2015, at 12:34 PM, Bryan Drewery wrote:
>
> On 10/17/15 11:25 AM, Ian Lepore wrote:
>> On Fri, 2015-10-16 at 14:04 +, Cy Schubert wrote:
>>> Author: cy
>>> Date: Fri Oct 16 14:04:16 2015
>>> New Revision: 289421
>>> URL:
On Sat, 2015-10-17 at 13:19 -0600, Warner Losh wrote:
> Until the next leap second…. It would be better to just
> always try to grab the latest one… Can we put something
> in periodic to do that so users that have releases
> that are older than 6 months aren’t screwed?
>
> Warner
>
I think
On Sat, Oct 17, 2015 at 12:25:50PM -0600, Ian Lepore wrote:
> If the leapseconds file is present, the leap bits for reference
> clocks and downstratum servers are ignored.
>
> I can't determine from casual code examination (and I don't have time
> to experiment now) whether that is true
Author: cy
Date: Fri Oct 16 14:04:16 2015
New Revision: 289421
URL: https://svnweb.freebsd.org/changeset/base/289421
Log:
Add default leap-seconds file. This should help ntp networks get the
leap second date correct
Updates to the file can be obtained from ftp://time.nist.gov/pub/ or
20 matches
Mail list logo