change CLOCK_REALTIME to CLOCK_MONOTONIC because it is more robust #44
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The
fenster_timefunction should useCLOCK_MONOTONICinstead ofCLOCK_REALTIMEas the argument toclock_gettime, since this is "not affected by discontinuous in the system time (e.g., if the system manually changes the clock)[...] All CLOCK_MONOTONIC variants guarantee that the time returned by consecutive calls will not go backwards". (man page)This is in contrast to the currently used
CLOCK_REALTIME, which is affected by such jumps.