summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar http://joeyh.name/ <http://joeyh.name/@web>2013-07-22 21:41:01 +0000
committerGravatar admin <admin@branchable.com>2013-07-22 21:41:01 +0000
commitb808e806f8456076d0f71a27f1e32a39fe87598a (patch)
tree849318df04b87dfb22762c9e01a4be27d22f6862
parent346fada433a3c2f4f2dec6d9b1c7cd566f506442 (diff)
Added a comment
-rw-r--r--doc/bugs/gpg_hangs_on_glacier_remote_creation/comment_1_41ca74a4e4aaf4f6b012a92677037651._comment14
1 files changed, 14 insertions, 0 deletions
diff --git a/doc/bugs/gpg_hangs_on_glacier_remote_creation/comment_1_41ca74a4e4aaf4f6b012a92677037651._comment b/doc/bugs/gpg_hangs_on_glacier_remote_creation/comment_1_41ca74a4e4aaf4f6b012a92677037651._comment
new file mode 100644
index 000000000..2dae713b0
--- /dev/null
+++ b/doc/bugs/gpg_hangs_on_glacier_remote_creation/comment_1_41ca74a4e4aaf4f6b012a92677037651._comment
@@ -0,0 +1,14 @@
+[[!comment format=mdwn
+ username="http://joeyh.name/"
+ ip="4.154.1.10"
+ subject="comment 1"
+ date="2013-07-22T21:41:01Z"
+ content="""
+I have tried but have not had any luck reproducing this when initializing a glacier remote.
+
+Do you also get this problem if you initialize a special remote of another type, such as the directory special remote, that's encrypted to the same gpg key?
+
+Can you reproduce the hang using the [[/install/Linux_standalone]] tarball?
+
+You should be able to tell which file descriptor gpg is blocking on. Just attach strace to the gpg process, and see what file descriptor it says gpg is reading from (or perhaps writing to). Since git-annex feeds it both a passphrase and data to encrypt, knowing the number of the file descriptor will narrow down the bug's cause.
+"""]]