Am Donnerstag, 11. November 2010, 16:16:10 schrieb Andrew: > 11.11.2010 14:04, KP Kirchdoerfer пишет: > > Am Donnerstag, 11. November 2010, 12:04:20 schrieb Andrew: > >> Hi all. > >> I tried to test bb ntpd how it works. Unfortunatelly, for me it can't > >> set system time: > >> > >> # ntpd -d -n -p 10.255.0.2 > >> ntpd: sent query to 10.255.0.2 > >> ntpd: reply from 10.255.0.2: reach 0x01 offset -10.105435 delay 0.003906 > >> status 0x24 strat 4 refid 0x0c00ff0a rootdelay 0.009506 > >> ntpd: sent query to 10.255.0.2 > >> ntpd: reply from 10.255.0.2: reach 0x03 offset -10.105610 delay 0.003906 > >> status 0x24 strat 4 refid 0x0c00ff0a rootdelay 0.009506 > >> ntpd: sent query to 10.255.0.2 > >> ntpd: reply from 10.255.0.2: reach 0x07 offset -10.105678 delay 0.003906 > >> status 0x24 strat 4 refid 0x0c00ff0a rootdelay 0.009506 > >> ntpd: sent query to 10.255.0.2 > >> ntpd: reply from 10.255.0.2: reach 0x0f offset -10.105748 delay 0.003906 > >> status 0x24 strat 4 refid 0x0c00ff0a rootdelay 0.009506 > >> ntpd: sent query to 10.255.0.2 > >> ntpd: reply from 10.255.0.2: reach 0x1f offset -10.105855 delay 0.003906 > >> status 0x24 strat 4 refid 0x0c00ff0a rootdelay 0.009506 > >> ntpd: sent query to 10.255.0.2 > >> ntpd: reply from 10.255.0.2: reach 0x3f offset -10.106034 delay 0.003906 > >> status 0x24 strat 4 refid 0x0c00ff0a rootdelay 0.009506 > >> ^C > >> > >> W/o debug - same situation, daemon still hangs in memory and actually > >> does nothing. No matter which clock offset is between hosts - 10 sec or > >> 2 hours. > >> > >> This is only my trouble, or not? > > > > Works for me > > (set time 5min back to test) > > > > ntpd -d -l -n -p 0.pool.ntp.org -p 1.pool.ntp.org > > ntpd: sent query to 131.188.3.220 > > ntpd: sent query to 141.40.103.101 > > ntpd: reply from 131.188.3.220: reach 0x01 offset 348.957963 delay > > 0.031876 status 0x24 strat 1 refid 0x00535047 rootdelay 00 > > [...] > > ntpd: reply from 131.188.3.220: reach 0x3f offset 348.959155 delay > > 0.032496 status 0x24 strat 1 refid 0x00535047 rootdelay 00 > > > > _ntpd: setting clock to Thu Nov 11 11:47:07 UTC 2010 (offset > > 348.958247s)_ > > > > > > ntpd: reply from 141.40.103.101: reach 0x01 offset 174.479370 delay > > 348.998325 status 0x24 strat 2 refid 0x12032286 rootdela2 > > ntpd: sent query to 131.188.3.220 > > ntpd: sent query to 141.40.103.101 > > > > ntpd: reply from 131.188.3.220: reach 0x01 offset 0.005073 delay 0.032078 > > status 0x24 strat 1 refid 0x00535047 rootdelay 0.00 > > ntpd: reply from 141.40.103.101: reach 0x03 offset 0.004849 delay > > 0.038722 status 0x24 strat 2 refid 0x12032286 rootdelay 0.2 > > > > kp > > How long ntpd tries to sync time before it finally set?
It's pretty fast I change date and then start ntpd. With a running ntp and an offset of 10min up to four, five minutes. Maybe it's faster if I use more than two peers. See busybox/networking/ntpd.c for more information how it works and how long it may take. kp ------------------------------------------------------------------------------ Centralized Desktop Delivery: Dell and VMware Reference Architecture Simplifying enterprise desktop deployment and management using Dell EqualLogic storage and VMware View: A highly scalable, end-to-end client virtualization framework. Read more! http://p.sf.net/sfu/dell-eql-dev2dev _______________________________________________ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
