From 7c01b694986a64d90973d8d1aa359d909d9f48d0 Mon Sep 17 00:00:00 2001 From: Dan Helfman Date: Tue, 11 Jun 2019 21:35:43 -0700 Subject: [PATCH] Details on where to view logs. --- docs/how-to/inspect-your-backups.md | 6 +++++- docs/how-to/set-up-backups.md | 4 ++-- 2 files changed, 7 insertions(+), 3 deletions(-) diff --git a/docs/how-to/inspect-your-backups.md b/docs/how-to/inspect-your-backups.md index bafcf9079..c8774a6d7 100644 --- a/docs/how-to/inspect-your-backups.md +++ b/docs/how-to/inspect-your-backups.md @@ -36,7 +36,11 @@ borgmatic --info ## Logging By default, borgmatic logs to a local syslog-compatible daemon if one is -present. You can customize the log level used for syslog logging with the +present. Where those logs show up depends on your particular system. If you're +using systemd, try running `journalctl -xe`. Otherwise, try viewing +`/var/log/syslog` or similiar. + +You can customize the log level used for syslog logging with the `--syslog-verbosity` flag, and this is independent from the console logging `--verbosity` flag described above. For instance, to disable syslog logging except for errors: diff --git a/docs/how-to/set-up-backups.md b/docs/how-to/set-up-backups.md index fd18b1c2c..bb368bcb0 100644 --- a/docs/how-to/set-up-backups.md +++ b/docs/how-to/set-up-backups.md @@ -109,8 +109,8 @@ This command's exit status (`$?` in Bash) is zero when configuration is valid and non-zero otherwise. Validating configuration can be useful if you generate your configuration -files via configuration management, or you just want to double check that your -hand edits are valid. +files via configuration management, or you want to double check that your hand +edits are valid. ## Initialization