upsmon et al: introduce NOTIFY_SUSPEND_TIMEJUMP_UNEXPECTED#3517
Open
jimklimov wants to merge 1 commit into
Open
upsmon et al: introduce NOTIFY_SUSPEND_TIMEJUMP_UNEXPECTED#3517jimklimov wants to merge 1 commit into
jimklimov wants to merge 1 commit into
Conversation
…e NOTIFY_SUSPEND_TIMEJUMP_UNEXPECTED [networkupstools#3405] Signed-off-by: Jim Klimov <jimklimov+nut@gmail.com>
|
A ZIP file with standard source tarball and another tarball with pre-built docs for commit 6f0d2bc is temporarily available: NUT-tarballs-PR-3517.zip. |
|
✅ Build nut 2.8.5.4909-master completed (commit 6c51166c59 by @jimklimov)
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Addresses: #3405
We have reports of various OS platforms reporting that they awoke from hibernation when none such happened. This may be in fact due to unified handling of unexpected time jumps, e.g. when a system is under such heavy load that it spends much more than
upsmonloop delay between actual runs of the loop cycles, or clock jumps due to NTP vs. RTC, etc.Either way, for a few recent NUT releases
upsmontries to handle this gracefully by re-querying UPS status before issuing FSD right away. The possibly misleading messages about awakening with little further explanation are however annoying. This PR adds an explicit notification to help make sense of these events.