From 3dc06c8067a387ff19b35213e77dbb7ceea5f630 Mon Sep 17 00:00:00 2001 From: Paride Legovini Date: Sun, 29 Jul 2018 18:16:10 +0200 Subject: [PATCH] documentation: btrbk.conf.5: clarify behavior of 'snapshot_create ondemand' when there are multiple targets --- doc/btrbk.conf.5.asciidoc | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/doc/btrbk.conf.5.asciidoc b/doc/btrbk.conf.5.asciidoc index 3294aab..5f6a058 100644 --- a/doc/btrbk.conf.5.asciidoc +++ b/doc/btrbk.conf.5.asciidoc @@ -155,12 +155,12 @@ Note that using ``long-iso'' has implications on the scheduling, see ``onchange'', snapshots are only created if the source subvolume has changed since the last snapshot (more precisely: if the btrfs generation has been increased since the last snapshot). If set to - ``ondemand'', snapshots are only created if the target subvolume - is reachable (useful if you are tight on disk space and you only - need btrbk for backups to an external disk which is not always - connected). If set to ``no'', the snapshots are never created - (useful if another instance of btrbk is taking care of snapshot - creation). Defaults to ``always''. + ``ondemand'', snapshots are only created if at least one target + subvolume is reachable (useful if you are tight on disk space and + you only need btrbk for backups to an external disk which is not + always connected). If set to ``no'', the snapshots are never + created (useful if another instance of btrbk is taking care of + snapshot creation). Defaults to ``always''. *incremental* yes|no|strict:: If set, incremental backups are created. If set to ``strict'',