mirror of https://github.com/digint/btrbk
59d96420c8
Add configuration option transaction_syslog, which can be set to a short name of a syslog facility, like user or local5. Most of the ones besides localX do not really make sense, but whatever, let the user decide. The only logging that is relevant for logging to syslog is the logging generated inside sub action, so it's easy to hijack all messages in there and also send them to syslog if needed. All output is done via print_formatted, which expects a file handle. So, abuse a file handle to a string to be able to change as less code as needed for this feature. Since syslog already adds the timestamps for us, I added a syslog formatting pattern, which is very similar to tlog, omitting the timestap. |
||
|---|---|---|
| .. | ||
| FAQ.md | ||
| btrbk.1 | ||
| btrbk.conf.5 | ||
| ssh_filter_btrbk.1 | ||
| upgrade_to_v0.23.0.md | ||