diff options
author | David Mazieres <dm@uun.org> | 2016-09-17 10:53:38 -0700 |
---|---|---|
committer | David Mazieres <dm@uun.org> | 2016-09-17 10:53:38 -0700 |
commit | 377afd03fac3311f2205f982d10669efc84e6016 (patch) | |
tree | e374bb00e8389e41b81a068bbd458151dc4c4d8e | |
parent | fdd1429e42fba969380db0c8ac219ded7b0bd3fe (diff) |
update man page to provide more detail about -F
-rw-r--r-- | muchsync.1.md | 10 |
1 files changed, 9 insertions, 1 deletions
diff --git a/muchsync.1.md b/muchsync.1.md index 34b8321..ed72263 100644 --- a/muchsync.1.md +++ b/muchsync.1.md @@ -141,7 +141,15 @@ privacy reasons, you will need to run the following on each replica: that files in a maildir are never edited. -F disables certain optimizations so as to make muchsync at least check the timestamp on every file, which will detect modified files at the cost of a - longer startup time. + longer startup time. If muchsync dies with the error "message + received does not match hash," you likely need to run it with the + -F option. + + Note that if your software regularly modifies the contents of mail + files (e.g., because you are running offlineimap with "synclabels + = yes"), then you will need to use -F each time you run muchsync. + Specify it as a server option (after the server name) if the + editing happens server-side. \-r /path/to/muchsync : Specifies the path to muchsync on the server. Ordinarily, muchsync |