Date: Tue, 9 Oct 2018 08:42:55 +0200 (CEST) From: Wojciech Puchar <wojtek@puchar.net> To: Peter Jeremy <peter@rulingia.com> Cc: Wojciech Puchar <wojtek@puchar.net>, freebsd-hackers@freebsd.org Subject: Re: ntpd strange problem Message-ID: <alpine.BSF.2.20.1810090841430.41943@puchar.net> In-Reply-To: <20181009052924.GJ21091@server.rulingia.com> References: <alpine.BSF.2.20.1810041557330.94038@puchar.net> <20181005061829.GG21091@server.rulingia.com> <alpine.BSF.2.20.1810051122310.9032@puchar.net> <a31ca466-3ef6-8a66-10cc-1c24cd6dc928@FreeBSD.org> <alpine.BSF.2.20.1810062041490.7470@puchar.net> <1538855151.14264.54.camel@freebsd.org> <alpine.BSF.2.20.1810081315510.26846@puchar.net> <20181009052924.GJ21091@server.rulingia.com>
next in thread | previous in thread | raw e-mail | index | archive | help
>> Strange but today (4 days after i restarted ntpd) it seems to be in sync > > A couple of suggestions: > * (especially if you have an ADSL link): The NTP protocol assumes that > the path between the client and server are have symmetric timing. In i have gigabit connectivity with low and stable delays. so it's not this. > my experience, bulk uploads or downloads can cause significant path > delay asymmetries, which can confuse ntpd. > * You only have a single server and are therefore dependent on the > trustworthiness of that server. A few more servers could be useful. this server is quite (actually excellently) stable and i trust it.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.20.1810090841430.41943>