Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature request] Disable error logging by default #86

Closed
rare-magma opened this issue Mar 25, 2020 · 2 comments
Closed

[Feature request] Disable error logging by default #86

rare-magma opened this issue Mar 25, 2020 · 2 comments
Assignees
Labels
enhancement New feature or request
Milestone

Comments

@rare-magma
Copy link

Would it be possible to disable logging by default? The error.log is quite write intensive (a few writes per second) and has, in my opinion, little value to the end user.
What do you think?

@xxxserxxx xxxserxxx self-assigned this Apr 5, 2020
@xxxserxxx xxxserxxx added the enhancement New feature or request label Apr 5, 2020
@xxxserxxx xxxserxxx added this to the v3.5.1 milestone Apr 5, 2020
@xxxserxxx
Copy link
Owner

@whooperr ,

I left in debugging in the last version, and that may be the one you have. The logs should only include errors. The next minor update removes this -- it slipped in, and correcting a bad release by "fixing" binaries without issuing a new release turns out to me a massive PITA because of cascading changes to the downstream distribution channels (AUR, homebrew, Nix, etc). Long story short, I'm sorry about that, and if you can wait for v3.5.1 this should be resolved.

Are you in a position to compile from source and see if this reduces the logging? If so, please do and if the logs get quiet, please let me know by closing this. Otherwise, if you believe you're seeing spurious, non-error message in the log, please attach the log here and let me see what's being chatty -- I will either resolve it, or consider disabling the logs.

@xxxserxxx
Copy link
Owner

No response; closing as the log message in question (as described by #85) was fixed in trunk and will be addressed in the next release. Only true errors should be reported, and these I'd like to hear about.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants