Kaz Kylheku wrote: > I'm trying to set the time on a Linux system (x86 vmware virtual > machine). I'm running ``ntpd -dddddddd -g -q''. > > It's receiving packets from the server, reporting the offset, but > after a bunch of round trips, it quits without setting the clock: > > addto_syslog: select(): nfound=-1, error: Interrupted system call > addto_syslog: select(): nfound=-1, error: Interrupted system call > sendpkt(fd=17 dst=10.18.28.4, src=10.18.28.129, ttl=0, len=48) > transmit: at 15 10.18.28.129->10.18.28.4 mode 3 > poll_update: at 15 10.18.28.4 flags 0301 poll 6 burst 1 last 1 next 17 > read_network_packet: fd=17 length 48 from 0a121c04 10.18.28.4 > fetch_timestamp: system network time stamp: 1173592706.715188 > receive: at 15 10.18.28.129<-10.18.28.4 flags 19 restrict 000 > receive: at 15 10.18.28.129<-10.18.28.4 mode 4 code 1 auth 0 > clock_filter: n 8 off 2720390.670297 del 0.000975 dsp 0.000063 jit > 5.168251, age 0 > addto_syslog: select(): nfound=-1, error: Interrupted system call > addto_syslog: select(): nfound=-1, error: Interrupted system call > addto_syslog: no reply; clock not set > > The /etc/ntp.conf file is just this. I took out all restricts: > > driftfile /var/lib/ntp/drift > broadcastdelay 0.008 > authenticate yes > keys /etc/ntp/keys > server 10.18.28.4 iburst burst >
It's been a few years since I last worked with VMWare but ISTR that VMWare wants to control the clock. You can configure VMWare to run ntpd rather than one of the client operating systems. _______________________________________________ questions mailing list [email protected] https://lists.ntp.isc.org/mailman/listinfo/questions
