From c0a5defe6f6c9b927c482bf98d515e8aed1b4b8b Mon Sep 17 00:00:00 2001 From: Dan MacDonald Date: Sun, 15 Oct 2023 20:21:59 +0100 Subject: [PATCH] Edit testing and debugging --- Manual.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/Manual.md b/Manual.md index 8076e34..ea353af 100644 --- a/Manual.md +++ b/Manual.md @@ -29,13 +29,13 @@ Keeping this in mind can help make more sense of the options described here: mos ## Testing and debugging -Its recommended to always use `--verbose` to see whats going on. It makes debugging easier. +It's recommended to always use `--verbose` or `-v` to see whats going on. It makes debugging easier. -During initial setup and testing of a backup you should use `--test`. This will do all the read-only operations, but will not change anything. It will show you exactly what its going to do. +During initial setup and testing of a backup you should use `--test`. This will perform all the read-only operations, but will not change anything. It will show you exactly what it's going to do. -If you encounter a problem and want to see the exact ZFS commands, use `--debug`. This outputs all the underlying zfs-commands in a different color. To even see the output of each command, use `--debug-output`. +If you encounter a problem and want to see the exact ZFS commands, use `--debug`. This outputs all the underlying zfs-commands in a different color. To see the output of each command, use `--debug-output`. -Note that debug mode will abort on the first failed dataset, and show a stacktrace. So its not recommended in production. +Note that debug mode will abort on the first failed dataset, and show a stacktrace so it's not recommended for use in production. ## Source and target SSH