[email protected] writes: > On Wednesday, February 11, 2015 at 3:40:02 PM UTC+8, Harlan Stenn wrote: > > [email protected] writes: > > > When I change ntp servers by "toish setobject cfg.ntp.servers 192.168.1.1 > 01" > > > in linux, ntp server print logs "localhost: timed out, nothing received", > the > > > ntp server change fails. Why is that ? > > > Appreciate so much for your help. > > > > What sort of 'restrict' lines do you have in your ntp.conf file? > > > > I have no idea what "toish ..." does. > > > > H > > Hi, the restrict line is:driftfile /etc/ntp.drift > restrict default ignore > restrict 127.0.0.1 > broadcastdelay 0.008
Are you using broadcasts to set the time? If not, you don't need the above line. > #6000000000s because we start at 1970 > tinker panic 6000000000 I would not do this. Starting ntpd with -g will ignore the panic gate for the first "time set". > restrict 192.168.1.101 nomodify notrap > server 192.168.1.101 minpoll 3 maxpoll 4 > The toish is a tool made by our system, the purpose of "toish > setobject cfg.ntp.servers 192.168.1.101" is to change the ntp server. > I've searched and find that the time out error may be related to > ntpdc's deprecation. Since when I change the server, ntpdc should > remove the old server from the remote serverlist and add the new > server to it, during which, a time out error occurs. So now the > problem is how can I still use ntpdc, it will be really huge task if I > use ntpq to replace it in our system so I don't want to give it up at > present. You don't want to use ntpdc for this. You want to use ntpq instead. Or perhaps you could use a "pool" directive that points to a local DNS name that contains an updated list of servers you want your clients to talk to. H _______________________________________________ questions mailing list [email protected] http://lists.ntp.org/listinfo/questions
