summaryrefslogtreecommitdiff
path: root/yarn.1.in
diff options
context:
space:
mode:
Diffstat (limited to 'yarn.1.in')
-rw-r--r--yarn.1.in18
1 files changed, 9 insertions, 9 deletions
diff --git a/yarn.1.in b/yarn.1.in
index f1708d9..6df8f15 100644
--- a/yarn.1.in
+++ b/yarn.1.in
@@ -62,21 +62,21 @@ The backup scenario from above might be implemented as follows:
.IP
.nf
IMPLEMENTS GIVEN some live data in a directory
-rm -rf "$TESTDIR/data"
-mkdir "$TESTDIR/data"
-echo foo > "$TESTDIR/data/foo"
+rm -rf "$DATADIR/data"
+mkdir "$DATADIR/data"
+echo foo > "$DATADIR/data/foo"
.IP
IMPLEMENTS GIVEN an empty backup repository
-rm -rf "$TESTDIR/repo"
-mkdir "$TESTDIR/repo"
+rm -rf "$DATADIR/repo"
+mkdir "$DATADIR/repo"
.IP
IMPLEMENTS WHEN a backup is made
-backup-program -r "$TESTDIR/repo" "$TESTDIR/data"
+backup-program -r "$DATADIR/repo" "$DATADIR/data"
.IP
IMPLEMENTS THEN the data can be restored
-mkdir "$TESTDIR/restored"
-restore-program -r "$TESTDIR/repo" "$TESTDIR/restored"
-diff -rq "$TESTDIR/data" "$TESTDIR/restored"
+mkdir "$DATADIR/restored"
+restore-program -r "$DATADIR/repo" "$DATADIR/restored"
+diff -rq "$DATADIR/data" "$DATADIR/restored"
.IP
IMPLEMENTS FINALLY cleanup
echo nothing to do, actually