Repository navigation
fix: stop the status service from flooding the log (v0.4.1) - #66
Merged
Merged
Conversation
The status service exited after printing `wg show`, so s6 restarted it every ~30 seconds. It now logs the WireGuard status once at startup with log_level info, periodically only with debug/trace, and never with notice or higher; the service no longer exits. - docs: new Logging section, updated Local Development section - bump version to 0.4.1 and add changelog
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
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.
Summary
Release v0.4.1.
The status service printed
wg showto the log every ~30 seconds: the script exited after each run and s6 restarted it. Now the service never exits and the output depends onlog_level:log_leveltrace,debuginfo(default)noticeand aboveChanges
services.d/status/run: new logic described above.DOCS.md: new Logging section (log_level, status output, iptables backend log); Local Development updated for the5-appsdevcontainer (it still referenced the removeddevcontainer_bootstrap).config.yaml: version 0.4.1;CHANGELOG.mdentry.Test plan
wg, 3.5 intervals per level:notice→ 0 prints,info→ 1 print,debug→ 3 prints; the service keeps running in all casesconfig.yamlonmainsays 0.4.1)