ntppool-agent: Raise criticality of two log messages - #11
Merged
Merged
Conversation
So they are rendered even if minimal system log level is raised to filter out levels Info and below - Log version string upon startup - Log when it's suspected clock might not be ok, and monitoring is paused
demsbjf8
force-pushed
the
raise-criticality-of-two-log-messages
branch
from
September 21, 2026 10:38
46a7eb6 to
ca0d267
Compare
Member
|
nice, thank you. |
Contributor
Author
|
With pleasure :-) |
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.
So they are rendered even if minimal system log level is raised to filter out levels Info and below
Maybe an even higher log level would be warranted for one, or both messages.