psw/borgmatic
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Details on where to view logs.

Browse source
This commit is contained in:
Dan Helfman 2019-06-11 21:35:43 -07:00
parent 4f0d3bf4ed
commit 7c01b69498
2 changed files with 7 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
docs/how-to/inspect-your-backups.md
View file

@ -36,7 +36,11 @@ borgmatic --info
## Logging ## Logging
By default, borgmatic logs to a local syslog-compatible daemon if one is 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 `--syslog-verbosity` flag, and this is independent from the console logging
`--verbosity` flag described above. For instance, to disable syslog logging `--verbosity` flag described above. For instance, to disable syslog logging
except for errors: except for errors:

4
docs/how-to/set-up-backups.md
View file

@ -109,8 +109,8 @@ This command's exit status (`$?` in Bash) is zero when configuration is valid
and non-zero otherwise. and non-zero otherwise.
Validating configuration can be useful if you generate your configuration Validating configuration can be useful if you generate your configuration
files via configuration management, or you just want to double check that your files via configuration management, or you want to double check that your hand
hand edits are valid. edits are valid.
## Initialization ## Initialization