-
-
Notifications
You must be signed in to change notification settings - Fork 757
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
debug log all cache / index full paths #5963
Comments
Can I work on this issue if it's still open? |
@Rsakhuja sure, just take it! :-) |
@Rsakhuja are you still working upon this issue |
@sumeetdeveloper if there is no response, i think we can just assume they are not working on this. |
Shall I start working upon this issue then? if it is open? |
Guess so, it's been a while since October. Thanks for helping! |
@ThomasWaldmann can you help me to reproduce this issue or point any documentation or stuff |
@sumeetdeveloper Sure. To start, just do a global search for cache_dir in the source. |
@ThomasWaldmann How would you like this to be implemented? Should there be another command that logs the cache dir by using the |
@diivi read how the ticket linked from top post ended. quite some work there could have been avoided if it were clear that it used a different cache dir than the user thought it did. maybe the user would have found the issue themselves, if --debug had output the full cache file path. |
Considering issues like #5954 are bad to solve / debug without this information, borg should debug log full paths of all caches / indexes it uses.
The text was updated successfully, but these errors were encountered: