On 9/28/2018 21:58 PM, Gary E. Miller via devel wrote:
No every OS, not even every Linux, uses systemd. NTPsec needs generic
solutions.
I'm aware. But it can be an option, included, of course. The ntpsec source
includes SystemV startup files, systemd startup and timers, xBSD startup,
etc. It
Yo Paul!
On Fri, 28 Sep 2018 21:32:28 -0700
Paul Theodoropoulos via devel wrote:
> A crafty way to avoid the 'every x on the x' problem of cron jobs -
> which can contribute to such 'success disasters' - might be to employ
> the systemd timer functionality for leapfetch,
No every OS, not even e
On 9/28/2018 20:56 PM, Hal Murray wrote:
Agreed, mostly. There is a big difference between the traffic from a few
geeks occasionally downloading a file and a swarm of systems downloading from
a cron job.
Years ago, a friend introduced me to a great term. I asked him what happens
if his applica
> I've sent a communication to NIST asking if they'd be willing to host the
> leap-seconds.list on an https link in addition to the existing ftp source.
Thanks.
The other approach is to get IETF to update their copy in a timely fashion.
That's probably as simple as finding out who to poke.
On 9/28/2018 19:06 PM, Hal Murray via devel wrote:
Plan B would be to host a copy of the file ourselves. Then we can update it
as appropriate and we can beef up the server if the load becomes significant.
That's a commitment to long term service.
I'm just a random jackass on the Internet, so hap
> Let me know if the above source should be used instead and I'll make
> the merge request.
We shouldn't publish URLs in something that will get widely distributed/used
without checking with the owner.
Plan B would be to host a copy of the file ourselves. Then we can update it
as appropriate
>
> On 29 Sep 2018, at 00:03, James Browning via devel wrote:
>
>> On Fri, Sep 28, 2018 at 3:42 PM Hal Murray via devel
>> wrote:
>>
>> The recent ftp=>https change to ntpleapfetch also changed the host from NIST
>> to IETF.
>>
>> -LEAPSRC="ftp://ftp.nist.gov/pub/time/leap-seconds.list";
>>
On Fri, Sep 28, 2018 at 3:42 PM Hal Murray via devel
wrote:
>
> The recent ftp=>https change to ntpleapfetch also changed the host from
> NIST
> to IETF.
>
> -LEAPSRC="ftp://ftp.nist.gov/pub/time/leap-seconds.list";
> +LEAPSRC="https://www.ietf.org/timezones/data/leap-seconds.list";
>
> The IETF
