From: Gerd Hoerst <gerd@hoerst.net>
To: development@lists.ipfire.org
Subject: Re: Opinions on chrony? (was: Re: chrony)
Date: Mon, 04 Jan 2021 11:21:47 +0100 [thread overview]
Message-ID: <d253dfe5-531c-86af-e780-8656ef235221@hoerst.net> (raw)
In-Reply-To: <20201231123834.GA256852@vesikko.tarvainen.info>
[-- Attachment #1: Type: text/plain, Size: 1464 bytes --]
Hi !
on my ipfire is use it since 4 or 5 weeks.. but i also have to use
https://github.com/dorchain/dcfshm
because i use a gude usb II dcf clock.
(on my 2 raspberry pi i use gpsd an pps signal)
So do i have to create a second package for this ?
Ciao Gerd
Am 31.12.2020 um 13:38 schrieb Tapani Tarvainen:
> I would prefer switching to chrony, primarily because it is indeed
> better with intermittent connections. NTS would be nice, too, but
> of little practical value at the moment.
>
> But I don't see it all that important or urgent, ntpd works well
> enough for almost all, so I would not prioritize it very high.
>
> Tapani Tarvainen
>
> On Thu, Dec 31, 2020 at 11:56:21AM +0100, Peter Müller (peter.mueller(a)ipfire.org) wrote:
>> Hello development folks,
>>
>> since Gerd has worked on chrony, which is believed to be more robust in case of unstable
>> internet connections (which possibly affects some IPFire users) than ntpd is, I eventually
>> thought whether or not replacing ntpd with chrony was worth the effort.
>>
>> Another motivation would be chrony's support for NTS, however, there is no thing like a
>> distributed NTS pool as of today. Cloudflare and Netnod are providing public NTS servers,
>> and probably some others do so as well, but I really would like to have a decentralised
>> pool before switching to NTS.
>>
>> Any thoughts on this?
>>
>> Thanks, and best regards,
>> Peter Müller
next parent reply other threads:[~2021-01-04 10:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20201231123834.GA256852@vesikko.tarvainen.info>
2021-01-04 10:21 ` Gerd Hoerst [this message]
[not found] <ec2acb55-cbd6-3710-3f5b-a7b94fd71802@ipfire.org>
2021-01-07 12:31 ` Michael Tremer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d253dfe5-531c-86af-e780-8656ef235221@hoerst.net \
--to=gerd@hoerst.net \
--cc=development@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox