[Busybox version is rather old (v1.31.0) and the kenel is 2.6.33.7] I'm using busybox ntpd and it appears to be working except for the fact that the return value from the adjtimex() kernel system call almost always returns TIME_ERROR and status bits of PLL UNSYNC [and sometimes FREQHOLD].
Once avery 64 seconds, ntpd polls the server, and the adjtimex() return is TIME_OK for a fraction of a second with status bits of PLL [sometimes FREQHOLD]. After a fraction of a second it returns to return of TIME_ERROR with the UNSYNC status bit set until the next poll. It looks like usually the FREQHOLD status bit comes on initially and then goes away after several minutes — but it sometimes comes back on later. The UNSYNC bit is always set except for a fraction of second after each ntp poll. Is this the expected behavior? I'm trying to determin from an application whether or not the system time (no RTC, so it always boots up in 1970) has been synchronized by ntpd or not. Do I just wait for the first time the UNSYNC bit goes away and assume the system time is OK after that? Or is the setting of the PLL bit good enough to indicate that the system time has been set by ntpd? -- Grant _______________________________________________ busybox mailing list [email protected] https://lists.busybox.net/mailman/listinfo/busybox
