Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bug #18

Open
ssfking opened this issue Mar 27, 2015 · 2 comments
Open

Bug #18

ssfking opened this issue Mar 27, 2015 · 2 comments

Comments

@ssfking
Copy link

ssfking commented Mar 27, 2015

When [NetworkClock sharedNetworkClock] is first called when there is no internet connection, no network associations will be created, meaning that no timers are ever created, so even when internet is back on at a later point in time, nothing will happen / no pings to any time servers will happen.

@gavineadie
Copy link
Collaborator

I'd be interested in other users' opinions on this.

Mine is that determining the presence of network connectivity is not the responsibility of NTP. While ios-ntp is a severely cut down version of the canonical NTP code and already makes exceptions (and could make this one), I'm reluctant to move this far away the core time protocol function.

@warpling
Copy link

I'm trying to prevent clock-cheating using ios-ntp so I appreciate anything that makes ios-ntp a smarter, reliable clock aware of it's "surroundings". That said I don't know much about the NTP standard itself.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants