From 2f7e79ace63dd1cd13b73b545e57c27e96398e99 Mon Sep 17 00:00:00 2001 From: Axel Burri Date: Thu, 20 Aug 2020 18:53:46 +0200 Subject: [PATCH] documentation: mention up-to-date status --- doc/btrbk.conf.5.asciidoc | 19 ++++++++++--------- 1 file changed, 10 insertions(+), 9 deletions(-) diff --git a/doc/btrbk.conf.5.asciidoc b/doc/btrbk.conf.5.asciidoc index c66272f..a4050c3 100644 --- a/doc/btrbk.conf.5.asciidoc +++ b/doc/btrbk.conf.5.asciidoc @@ -140,15 +140,16 @@ Note that using ``long-iso'' has implications on the scheduling, see *snapshot_create* always|onchange|ondemand|no:: 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 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''. + ``onchange'', snapshots are only created if the last snapshot is + not up-to-date, i.e. the source subvolume has changed (more + precisely: the btrfs generation has been increased) since the last + snapshot was created. If set to ``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'',