Miroslav Lichvar wrote:
On Mon, Feb 16, 2015 at 12:56:27PM +0000, David Lord wrote:
I've just fetched chrony-2.0-pre1. It seemed to compile and
install ok on NetBSD-6/i386. The client IS one of the servers
configured in chrony.conf and it behaved same as with 1.31.
I didn't know this was such a common configuration.
As a workaround you can add "acquisitionport 123" to chrony.conf to
use just one socket for all (client, peer, server) communication,
which will effectively disable the check in which the server's request
is failing.
Done and ready for next restart.
That was it, as restart after the client had been removed from
chrony.conf the client picked up a reply from chrony. So that
bug still needs fixing.
I'm not sure what's wrong, it seems to be working for me with
2.0-pre1.
Nothing wrong, it started working ok after I had removed that
client from the config file. I'd just used the same server
lines as I had in my ntp.conf. Assuming "acquisitionport 123"
works I can use the same peer and server lines.
thanks
David
_______________________________________________
questions mailing list
[email protected]
http://lists.ntp.org/listinfo/questions
