On Mon, Feb 16, 2015 at 03:51:07PM +0000, David Lord wrote: > Miroslav Lichvar wrote: > >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.
Apparently, that workaround is not usable with 1.31, sorry for the noise. > >>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 meant with 2.0-pre1 the clients should be getting responses even if they are configured as servers in chrony.conf with otherwise standard configuration. It seems to work for me. If it doesn't for you, can you please post your chronyd -d -d output? -- Miroslav Lichvar _______________________________________________ questions mailing list [email protected] http://lists.ntp.org/listinfo/questions
