From mboxrd@z Thu Jan  1 00:00:00 1970
From: Tapani Tarvainen <ipfire@tapanitarvainen.fi>
To: development@lists.ipfire.org
Subject: Re: Migrating from ntp to chrony - challenge
Date: Tue, 06 Jul 2021 19:42:19 +0300
Message-ID: <20210706164219.GA81047@vesikko.tarvainen.info>
In-Reply-To: <299e92f1871d570cb46d79c22c3689fd@ipfire.org>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============2579945635890591734=="
List-Id: <development.lists.ipfire.org>

--===============2579945635890591734==
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable


On Tue, Jul 06, 2021 at 03:08:25PM +0200, Arne Fitzenreiter (arne_f(a)ipfire.=
org) wrote:
>=20
> If you change from ntp keep in mind that we need ntpdate for the settime
> skript which is used by unbound to syncronize the time with a given IP
> address if the time is incorrect and DNS not working becasue the wrong
> time breaks DNSSec.
> This is common on system without RTC Battery.
>=20
> Not sure if chrony can handle this at all.

It can, with the somewhat odd syntax

chronyd -q 'server 162.159.200.1 iburst'

That is effectively equivalent to

ntpdate 162.159.200.1

--=20
Tapani Tarvainen

--===============2579945635890591734==--