diff --git a/NEWS b/NEWS index 46f1cd0e0..f8e17da85 100644 --- a/NEWS +++ b/NEWS @@ -2,6 +2,7 @@ * #316: Fix hang when a stale database dump named pipe from an aborted borgmatic run remains on disk. * Tweak comment indentation in generated configuration file for clarity. + * Link to Borgmacator GNOME AppIndicator from monitoring documentation. 1.5.5 * #314: Fix regression in support for PostgreSQL's "directory" dump format. Unlike other dump diff --git a/docs/how-to/monitor-your-backups.md b/docs/how-to/monitor-your-backups.md index 9f6d9ca28..af9c9d0b5 100644 --- a/docs/how-to/monitor-your-backups.md +++ b/docs/how-to/monitor-your-backups.md @@ -42,6 +42,7 @@ below for how to configure this. software to consume borgmatic JSON output and track when the last successful backup occurred. See [scripting borgmatic](https://torsion.org/borgmatic/docs/how-to/monitor-your-backups/#scripting-borgmatic) +and [related software](https://torsion.org/borgmatic/docs/how-to/monitor-your-backups/#related-software) below for how to configure this. 5. **Borg hosting providers**: Most [Borg hosting providers](https://torsion.org/borgmatic/#hosting-providers) include @@ -250,6 +251,11 @@ suppressed so as not to interfere with the captured JSON. Also note that JSON output only shows up at the console, and not in syslog. +## Related software + + * [Borgmacator GNOME AppIndicator](https://github.com/N-Coder/borgmacator/) + + ### Successful backups `borgmatic list` includes support for a `--successful` flag that only lists diff --git a/docs/how-to/set-up-backups.md b/docs/how-to/set-up-backups.md index 6335a304d..f17f786f9 100644 --- a/docs/how-to/set-up-backups.md +++ b/docs/how-to/set-up-backups.md @@ -268,6 +268,7 @@ issues when reading files to backup. If that happens to you, you may be interested in an [unofficial work-around for Full Disk Access](https://projects.torsion.org/witten/borgmatic/issues/293). + ## Colored output Borgmatic produces colored terminal output by default. It is disabled when a @@ -276,6 +277,7 @@ non-interactive terminal is detected (like a cron job), or when you use the setting the environment variable `PY_COLORS=False`, or setting the `color` option to `false` in the `output` section of configuration. + ## Troubleshooting ### "found character that cannot start any token" error