ambiser
/
btrbk
mirror of https://github.com/digint/btrbk
9
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

doc: clarify behavior or 'snapshot_create ondemand' when there are multiple targets

pull/245/head
Paride Legovini 2018-07-29 18:16:10 +02:00
parent 0d124a4373
commit ba2280ca93
1 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
doc/btrbk.conf.5.asciidoc
View File

@ -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 If set to ``always'', snapshots are always created. If set to
``onchange'', snapshots are only created if the source subvolume ``onchange'', snapshots are only created if the source subvolume
has changed since the last snapshot (more precisely: if the btrfs has changed since the last snapshot (more precisely: if the btrfs
generation has been increased since the last snapshot). If set to generation has been increased since the last snapshot). If set
``ondemand'', snapshots are only created if the target subvolume to ``ondemand'', snapshots are only created at least one target
is reachable (useful if you are tight on disk space and you only subvolume is reachable (useful if you are tight on disk space and
need btrbk for backups to an external disk which is not always you only need btrbk for backups to an external disk which is not
connected). If set to ``no'', the snapshots are never created always connected). If set to ``no'', the snapshots are never created
(useful if another instance of btrbk is taking care of snapshot (useful if another instance of btrbk is taking care of snapshot
creation). Defaults to ``always''. creation). Defaults to ``always''.