From 87cae49e2943d3ee4284d8bf8f534cc8510e2276 Mon Sep 17 00:00:00 2001 From: Ayitaka Date: Mon, 12 Aug 2019 06:06:08 -0700 Subject: [PATCH] The way to properly set log level was changed. See: https://github.com/dani-garcia/bitwarden_rs/issues/428#issuecomment-485245645 --- Logging.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Logging.md b/Logging.md index eb743d8..3822a89 100644 --- a/Logging.md +++ b/Logging.md @@ -13,7 +13,7 @@ Note that if you're using the docker image, you'll most likely want to use a fil # Change the log level -To reduce the amount of log messages, you can set the log level to 'warn' (default is 'info'). The [Log level](https://docs.rs/log/0.4.7/log/enum.Level.html#variants) can be adjusted with the environment variable `LOG_LEVEL` while also setting `EXTENDED_LOGGING=true`. NOTE: Using the log level "warn" still allows [Fail2Ban](https://github.com/dani-garcia/bitwarden_rs/wiki/Fail2Ban-Setup) to work properly. +To reduce the amount of log messages, you can set the log level to 'warn' (default is 'info'). The [Log level](https://docs.rs/log/0.4.7/log/enum.Level.html#variants) can be adjusted with the environment variable `LOG_LEVEL` while also setting `EXTENDED_LOGGING=true`. NOTE: Using the log level "warn" or "error" still allows [Fail2Ban](https://github.com/dani-garcia/bitwarden_rs/wiki/Fail2Ban-Setup) to work properly. `LOG_LEVEL` options are: "trace", "debug", "info", "warn", "error" or "off".