From b808e806f8456076d0f71a27f1e32a39fe87598a Mon Sep 17 00:00:00 2001 From: "http://joeyh.name/" Date: Mon, 22 Jul 2013 21:41:01 +0000 Subject: Added a comment --- .../comment_1_41ca74a4e4aaf4f6b012a92677037651._comment | 14 ++++++++++++++ 1 file changed, 14 insertions(+) create mode 100644 doc/bugs/gpg_hangs_on_glacier_remote_creation/comment_1_41ca74a4e4aaf4f6b012a92677037651._comment 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. +"""]] -- cgit v1.2.3