Logging unclutter #615
Merged
Logging unclutter #615
Conversation
This file contains 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
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.
In an effort to unclutter the log files, I did followig small changes:
YACYto more descriptiveNETWORKfine(these many single-liners about DHT priority and RWI extensions are good only for debug, not for the regular run)fine(could beconfigas well, but there should be some granularity to distinguish between more important messages from these cluttering common ones)NETWORKcategory into the defaultyacy.loggingfileFINERandFINESTloglevels to default logging file, because they are used in the code, but not documentedCould be a part of solution for #611.
RWI and CRAWLER (as proposed in #414) should be categorised later and logging cleaned in a way that everything could be switched on/off by config file in a neat way.