On Wed, Dec 14, 2016 at 04:57:49PM +0100, Miroslav Lichvar wrote:
> On Wed, Dec 14, 2016 at 03:34:30PM +, Adri Koppes wrote:
> > Miroslav,
> >
> > I have chronyd 2.4.1 running on FreeBSD 11.0 release and it's working fine.
> > All refclocks are internet servers and data is received normally.
On Wed, 14 Dec 2016, Adri Koppes wrote:
Bill,
If you read the original message, chrony 2.4.1 is running without problems.
This implies the network is working, name resolutions is fine and the firewall
isn't blocking stuff.
I am the network and systems administrator, so I know it's ok!
The
William G. Unruh __| Canadian Institute for| Tel: +1(604)822-3273
Physics _|___ Advanced Research _| Fax: +1(604)822-5324
UBC, Vancouver,BC _|_ Program in Cosmology | un...@physics.ubc.ca
Canada V6T 1Z1 | and Gravity __|_ www.theory.physics.ubc.ca/
On Wed, 14 Dec 2016,
On Wed, Dec 14, 2016 at 03:34:30PM +, Adri Koppes wrote:
> Miroslav,
>
> I have chronyd 2.4.1 running on FreeBSD 11.0 release and it's working fine.
> All refclocks are internet servers and data is received normally.
> I have just compiled chrony 3.0-pre1 and it fails to receive any timestamp
Bill,
If you read the original message, chrony 2.4.1 is running without problems.
This implies the network is working, name resolutions is fine and the firewall
isn't blocking stuff.
I am the network and systems administrator, so I know it's ok!
The test with chrony 3.0-pre1 is also using the
Interesting! I would not have thought of this. Both the i211 and i354 have the
SDP pins. Not exactly a pre-made PPS input, but possible with some soldering
and some code.
Denny
> On Dec 13, 2016, at 23:21, Miroslav Lichvar wrote:
>
> On Tue, Dec 13, 2016 at 05:03:15PM
Btw, it might be good for Chrony to support configuration for corrections
similar to what is discussed in that thread:
delayAsymmetry - corrects for any asymmetry between the Rx and Tx paths
egressLatency - corrects the transmit latency at the MAC/PHY
ingressLatency - corrects the receive
On Wed, Dec 14, 2016 at 05:07:11PM +0100, Miroslav Lichvar wrote:
> I found the following commit, which would explain the problem:
>
> https://github.com/freebsd/freebsd/blob/3fa64907439c00965fb0cbb222a6bf073c452630/lib/libc/gen/recvmmsg.c
Ehm, this is the actual commit
Miroslav,
I have chronyd 2.4.1 running on FreeBSD 11.0 release and it's working fine.
All refclocks are internet servers and data is received normally.
I have just compiled chrony 3.0-pre1 and it fails to receive any timestamp data
from the internet refclocks.
I tried again with the latest
This is an automated email from git. It was generated because a ref
change was pushed to the "chrony/chrony.git" repository.
The branch, master has been updated
via 5634e6b963657a71758111ef66dc344705fa8bfa (commit)
via db312a5ff6696fe9eec4b14cce2aa2da4c0f550d (commit)
via
10 matches
Mail list logo