Hi, this patchset should fix this bug https://bugs.meego.com/show_bug.cgi?id=25486
If the timeserver cannot be contacted, then try next address. This is fixed in patch #1. I noticed that when resolving timeserver, if the DNS returns more than one IP address, then we do not try to check the other address if the first timeserver cannot be contacted. This is fixed in patch #2. We should accept NTP packet containing leap second flag set. This is fixed by patch #3. Cheers, Jukka Jukka Rissanen (3): ntp: If the server cannot be contacted, try next one timeserver: Try all resolved timeserver IP addresses ntp: Accept ntp packet containing leap second info src/ntp.c | 9 +++++++-- src/timeserver.c | 6 +++++- 2 files changed, 12 insertions(+), 3 deletions(-) -- 1.7.9.5 _______________________________________________ connman mailing list [email protected] http://lists.connman.net/listinfo/connman
