mirror of
https://github.com/borgbackup/borg.git
synced 2024-12-25 01:06:50 +00:00
226e5519f3
There are persistent questions why output from options like --list and --stats doesn't show up. Also, borg currently isn't able to show *just* the output for a given option (--list, --stats, --show-rc, --show-version, or --progress), without other INFO level messages. The solution is to use more granular loggers, so that messages specific to a given option goes to a logger designated for that option. That option-specific logger can then be configured separately from the regular loggers. Those option-specific loggers can also be used as a hook in a BORG_LOGGING_CONF config file to log the --list output to a separate file, or send --stats output to a network socket where some daemon could analyze it. Steps: - create an option-specific logger for each of the implied output options - modify the messages specific to each option to go to the correct logger - if an implied output option is passed, change the option-specific logger (only) to log at INFO level - test that root logger messages don't come through option-specific loggers They shouldn't, per https://docs.python.org/3/howto/logging.html#logging-flow but test just the same. Particularly test a message that can come from remote repositories. Fixes #526, #573, #665, #824 |
||
|---|---|---|
| .. | ||
| _static | ||
| borg_theme/css | ||
| misc | ||
| usage | ||
| api.rst | ||
| authors.rst | ||
| changes.rst | ||
| conf.py | ||
| deployment.rst | ||
| development.rst | ||
| faq.rst | ||
| global.rst.inc | ||
| index.rst | ||
| installation.rst | ||
| internals.rst | ||
| Makefile | ||
| quickstart.rst | ||
| resources.rst | ||
| support.rst | ||
| usage.rst | ||