From 6793dfb0d7e4fba307d7eed6fc587d144ce9d947 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Fri, 27 Feb 2015 14:56:47 -0400 Subject: [PATCH] response --- ...1_d56818a8f5b3a94ecf5159c76f24768c._comment | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) create mode 100644 doc/forum/Verification/comment_1_d56818a8f5b3a94ecf5159c76f24768c._comment diff --git a/doc/forum/Verification/comment_1_d56818a8f5b3a94ecf5159c76f24768c._comment b/doc/forum/Verification/comment_1_d56818a8f5b3a94ecf5159c76f24768c._comment new file mode 100644 index 0000000000..d9684d922d --- /dev/null +++ b/doc/forum/Verification/comment_1_d56818a8f5b3a94ecf5159c76f24768c._comment @@ -0,0 +1,18 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 1""" + date="2015-02-27T18:51:52Z" + content=""" +Well, it depends on how big the files are, but taking a few hours to sync +might indicate that your repositories are not immediately notifying +one-another of changes. It might be falling back to polling every half +an hour for new changes. + +You could fix that by setting up XMPP, or better, by installing git-annex +5.20140421 or newer on the SSH server; then the clients would immediately +notify when there are changes. + +You can find out if all files are present on the server by running +`git annex find --not --in $server` on one of the clients. Any files +it prints out have not been stored in the server. +"""]]