From eb31316d5c0bdab645853a400aa61b5b4eb63b54 Mon Sep 17 00:00:00 2001 From: "http://joeyh.name/" Date: Sun, 19 May 2013 19:35:51 +0000 Subject: Added a comment --- .../comment_8_178fd4e4d6abbca192fcd6d592615fca._comment | 12 ++++++++++++ 1 file changed, 12 insertions(+) create mode 100644 doc/bugs/git_annex_fork_bombs_on_gpg_file/comment_8_178fd4e4d6abbca192fcd6d592615fca._comment (limited to 'doc/bugs/git_annex_fork_bombs_on_gpg_file') diff --git a/doc/bugs/git_annex_fork_bombs_on_gpg_file/comment_8_178fd4e4d6abbca192fcd6d592615fca._comment b/doc/bugs/git_annex_fork_bombs_on_gpg_file/comment_8_178fd4e4d6abbca192fcd6d592615fca._comment new file mode 100644 index 000000000..38b136b37 --- /dev/null +++ b/doc/bugs/git_annex_fork_bombs_on_gpg_file/comment_8_178fd4e4d6abbca192fcd6d592615fca._comment @@ -0,0 +1,12 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + nickname="joey" + subject="comment 8" + date="2013-05-19T19:35:51Z" + content=""" +I've fixed the repeated \"(gpg)\" problem. But that is not the real problem... + +Looks to me like there is a problem with running gpg to extract the encryption key of the repository. I can cause the same \"resource vanished\" message if I make gpg exit 1 immediately when it starts. I also managed to get 3 zombies when failing to send 100 files. Although in my case they were gpg zombies, not git-annex zombies. + +Can you run `gpg` manually at the command line? If you installed git-annex from the OSX dmg file, you need to have used \"runshell\" to get the gpg that's included in it onto the PATH before you do this. +"""]] -- cgit v1.2.3