-
Notifications
You must be signed in to change notification settings - Fork 38
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
Disable debugging (for kbfs) #3155
Comments
Same thing on Linux. If you update the systemd configuration to remove the debug flag, it'll get added back in on the next reboot. I also couldn't find a setting in /etc/default/keybase that would disable this either. |
Use systemd drop-in units instead. For example,
, and
Note this is unsupported and we won't be able to help you if you run into issues (unless you turn on logs again and reproduce the bug). (I've updated these to remove only debugging) |
I don't want to disable all logging, because I want to catch errors. I just don't want debug logging. Debug logging on a laptop eats up measurable battery life (keybase is consistently higher than chrome, unless I simply remove "debug" from the systemd config). |
You can do that with drop-in units too. See https://askubuntu.com/a/659268. |
So that anyone reading the thread isn't confused: #3155 (comment) (including @heronhaye 's edit) does work, and survives both reboots and updates to keybase (tested on Ubuntu 19.04) |
Any updates on how to resolve this on macOS? |
@heronhaye Can this be done in Windows as well? |
Piping in a bit late, but I wonder as well how it's done under macOS. Same reason as @docsmooth — even though I haven't noticed much of a battery drain myself, but it's a question of not wasting resources — I'm not actively developing anything on top of Keybase (yet!) so I don't really need to deal with debugging logs, for now. Thanks for the systemd drop-in units tip, though; they're cool for the many devices and servers I've got around the world which do use |
I recently noticed that my
keybase.kbfs.log
andkeybase.service.log
files were nearing around 100MB in size, each. It appears that both contain quite a bit of [DEBU ] statements.When I run
keybase -d status
I can see that kbfs is started with the debug flag:/Applications/Keybase.app/Contents/SharedSupport/bin/kbfs -debug -log-file=/Users/crahan/Library/Logs/keybase.kbfs.log
Is there a way to disable this debug flag? Can we add
--no-debug
to the masterconfig.json
file to help prevent this. If so, can someone provide an example?The text was updated successfully, but these errors were encountered: