From: Alok Barsode <[email protected]>
If the NTP server failed to respond, NTP client wait for 16 seconds
before trying the next server. But since now we have the default
gateway as a possible candidate for NTP (which has higher priority over
global timeaservers), there might be a chance that it might fail to
respond to a NTP query (e.g a wifi router without ntp support).
We have to wait for 16 sec, untill NTP switches to the next server.
This seems like a long period, especially if you made timezone changes
and you want the NTP sync to happen asap. Hence reducing this timeout to
5 seconds.
---
src/ntp.c | 4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/src/ntp.c b/src/ntp.c
index cbe5a3b..481f045 100644
--- a/src/ntp.c
+++ b/src/ntp.c
@@ -359,11 +359,11 @@ int __connman_ntp_start(char *server)
start_ntp(timeserver);
/*
- * Add a fallback timeout , preferably longer, 16 sec here,
+ * Add a fallback timeout , preferably short, 5 sec here,
* to fallback on the next server.
*/
- timeout_id = g_timeout_add_seconds(16, next_server, NULL);
+ timeout_id = g_timeout_add_seconds(5, next_server, NULL);
return 0;
}
--
1.7.5.4
_______________________________________________
connman mailing list
[email protected]
http://lists.connman.net/listinfo/connman
