If you have no control of the server, how do you even know that your time is
off and not the server’s time? An application should never crash due to an
unexpected timestamp in a received packet, that’s bad programming.
Apart from that, if your machine synchronises itself over the internet, 50us
source*
On Mon, Nov 28, 2022 at 12:52:06PM +, MUZZULINI Frank wrote:
> Hi,
>
> This one really puzzles me:
> MS Name/IP address Stratum Poll Reach LastRx Last sample
> ===
> =x 192.168.42.1
Hi,
This one really puzzles me:
MS Name/IP address Stratum Poll Reach LastRx Last sample
===
=x 192.168.42.1 11 5 36738 +63.5s[ +63.5s] +/- 121us
=x 192.168.42.2 11 6
Also Red Hat 8 and all its derivatives.
In fact in EL8 Red Hat doesn’t even provide and ntpd-package as an alternative
anymore.
From: chengyechun
Sent: Freitag, 10. Juni 2022 03:40
To: chrony-users@chrony.tuxfamily.org
Subject: 答复: [chrony-users] Distros that use Chrony by default
*EXTERNAL
Hi Lonnie,
Using --help looks more natural and less dependent on how other options are
parsed:
ARG="" ; chronyc --help | grep -q -- -N && ARG="-N" ; chronyc $ARG sources
Regards,
Frank
-Original Message-
From: Lonnie Abelbeck
Sent: Freitag, 13. Dezember 2019 17:43
To:
Well, no daemon can be more precise than its sources.
I would use independent measurements against the same source(s) individually
using "ntpdate -q " and/or "chronyd -Q -f " (*). Preferably
both.
Regards,
Frank
(*) containing "server iburst"
-Original Message-
From: Miroslav
-Original Message-
From: Miroslav Lichvar [mailto:mlich...@redhat.com]
Sent: Freitag, 1. Februar 2019 16:25
To: chrony-users@chrony.tuxfamily.org
Subject: Re: [chrony-users] initstepslew seems to break chronyd
On Fri, Feb 01, 2019 at 02:58:09PM +, MUZZULINI Frank wrote:
> Hello Miros
[mailto:mlich...@redhat.com]
Sent: Freitag, 1. Februar 2019 10:50
To: chrony-users@chrony.tuxfamily.org
Subject: Re: [chrony-users] initstepslew seems to break chronyd
On Thu, Jan 31, 2019 at 04:48:00PM +, MUZZULINI Frank wrote:
> local stratum 11
> server 10.4.142.10 minpoll 5 maxpoll 8
Hi all,
A colleague asked me to investigate a problem with chrony on SL7.4.
The relevant part of the configuration file looks like this:
(We should probably add orphan to the local line, but that does not affect the
behaviour)
local stratum 11
server 10.4.142.10 minpoll 5 maxpoll 8 iburst prefer
