From ba2280ca93bfc45aaec9847705e8f2b2866d45fc Mon Sep 17 00:00:00 2001 From: Paride Legovini Date: Sun, 29 Jul 2018 18:16:10 +0200 Subject: [PATCH] doc: clarify behavior or 'snapshot_create ondemand' when there are multiple targets --- doc/btrbk.conf.5.asciidoc | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/doc/btrbk.conf.5.asciidoc b/doc/btrbk.conf.5.asciidoc index 3294aab..1621f74 100644 --- a/doc/btrbk.conf.5.asciidoc +++ b/doc/btrbk.conf.5.asciidoc @@ -154,11 +154,11 @@ Note that using ``long-iso'' has implications on the scheduling, see If set to ``always'', snapshots are always created. If set to ``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 + generation has been increased since the last snapshot). If set + to ``ondemand'', snapshots are only created 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''.