Fix generic server INFO log output entries at startup, even on higher log levels
#542
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.
Description
This PR fixes an issue (previously an ad-hoc and inconsistent behavior) where SWS was printing
INFOlevel messages at startup despite setting up a higher log level. E.g.,WARNorERROR.Notice:
For consistency reasons, SWS now won't persistently show server information at startup independently of the log level as it did before. Instead, those info log entries are non-persistent and under the normal server
INFOlog level.For example. To show those logs again then use the
INFOlog level.Related Issue
Resolves #541
Motivation and Context
How Has This Been Tested?
Screenshots (if appropriate):