btrbk icon indicating copy to clipboard operation
btrbk copied to clipboard

Bug: "--loglevel debug" NOT writes a single btrfs command to btrbk.log

Open Heavygrass opened this issue 6 months ago • 2 comments

Hi, sudo btrbk --loglevel debug --progress --config=$config_file run does NOT make btrbk to write a single btrfs command to /var/log/btrbk.log file.

I believe --loglevel trace doesn't do it either.

This is specifically about log file, not about console output.

btrbk command line client, version 0.33.0-dev.

Heavygrass avatar Jul 04 '25 20:07 Heavygrass

Btrbk logs go to stderr. What you refer to is transaction_log (logs snapshot and send-receive operations), which is not affected by --loglevel.

digint avatar Jul 05 '25 21:07 digint

@digint Thanks for your response.

Whats the relation (by design) between --verbose and --loglevel? man btbk only contains the below, which is very confusing. Does --verbose affect whats written to /var/log/btrbk.log? Could man page be more detailed?

-v, --verbose
           Increase the logging level, see "--loglevel".
-l, --loglevel <level>
           Set the level of verbosity for the stderr logging. Accepted levels are: error, warn, info, debug,
           and trace. Default is info.

Heavygrass avatar Jul 06 '25 01:07 Heavygrass