From 4ccaf753bacaa268306e6fd0346efdd02d59cc0b Mon Sep 17 00:00:00 2001 From: Darrin Chambers Date: Fri, 24 Aug 2018 15:27:09 -0700 Subject: [PATCH] Update index.md Minor word change/correction 'done' -> 'down' Should we list all available log categories? --- manual/invoking/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/manual/invoking/index.md b/manual/invoking/index.md index b120eed..17c9712 100644 --- a/manual/invoking/index.md +++ b/manual/invoking/index.md @@ -67,7 +67,7 @@ This might easily become too much. A particularly useful category is "Exec" whic lsyncd -log Exec CONFIGFILE {% endhighlight %} -When the initial startup sync fails by default Lsyncd will terminate with an error message. It has been designed this way, so configuration failures are visibly reported to a possibly beginning user. However, in production a remote target might be done, but you want Lsyncd to start nevertheless and keep trying to sync to the remote target until it is up. +When the initial startup sync fails by default Lsyncd will terminate with an error message. It has been designed this way, so configuration failures are visibly reported to a possibly beginning user. However, in production a remote target might be down, but you want Lsyncd to start nevertheless and keep trying to sync to the remote target until it is up. {% highlight shell %} lsyncd -insist -rsync /home/USER/src remotehost:dst