bac95a22940a1cfafeaa4fdb3cd6f70bb28fef16

Message

Updated README file to explain --dry-run and --debug

Diff

This diff is truncated to protect this page.

 1diff --git a/README.md b/README.md
 2index c634a911899da96bd9f78bc611f15014696898be..659425cd541a82ef3dcb6bcf9c5276c1a44f09c7 100644
 3--- a/README.md
 4+++ b/README.md
 5@@ -82,6 +82,7 @@ NOTE: to ease future updates of the script, you may prefer NOT to edit the scrip
 6             --backup-script        automatically backup the script and secret key to
 7                                    the current working directory
 8         -n, --dry-run              perform a trial run with no changes made
 9+        -d, --debug                echo duplicity commands to logfile
10 
11 
12 ## Usage Examples
13@@ -144,11 +145,11 @@ NOTE: to ease future updates of the script, you may prefer NOT to edit the scrip
14 
15 This script attempts to simplify the task of running a duplicity command; if you are having any problems with the script the first step is to determine if the script is generating an incorrect command or if duplicity itself is causing your error.
16 
17-To see exactly what is happening when you run duplicity-backup, either pass the option `-n` or `--dry-run` on the command line, or head to the bottom of the configuration file and uncomment the `ECHO=$(which echo)` variable. 
18+To see exactly what is happening when you run duplicity-backup, either pass the option `-d` or `--debug` on the command line, or head to the bottom of the configuration file and uncomment the `ECHO=$(which echo)` variable. 
19 
20 This will stop the script from running and will, instead, output the generated command into your log file. You can then check to see if what is being generated is causing an error or if it is duplicity causing you woe.
21 
22-