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

Use CLOCK_MONOTONIC instead of CLOCK_REALTIME #15

Closed
wants to merge 1 commit into from

Conversation

baruch
Copy link

@baruch baruch commented Sep 4, 2014

This prevents problems when the clock is jumping around which can happen
when NTP starts or in a misconfigured environment with multiple NTP
servers that are out of sync.

Closes #14

This prevents problems when the clock is jumping around which can happen
when NTP starts or in a misconfigured environment with multiple NTP
servers that are out of sync.
@baruch
Copy link
Author

baruch commented Sep 5, 2014

The time test fails. I'll look at it and reissue the MR.

@baruch baruch closed this Sep 5, 2014
@baruch baruch mentioned this pull request Sep 5, 2014
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

Successfully merging this pull request may close these issues.

Timeouts handled with real time clock instead of monotonic clock
1 participant