aboutsummaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorGravatar http://joeyh.name/ <joey@web>2013-05-19 19:35:51 +0000
committerGravatar admin <admin@branchable.com>2013-05-19 19:35:51 +0000
commiteb31316d5c0bdab645853a400aa61b5b4eb63b54 (patch)
treee62086f5c66798cb632c0423bb1b4e3f63f1b22a /doc
parentda55435c5bf34ffb6e73e833f1f8d41ef2d5e600 (diff)
Added a comment
Diffstat (limited to 'doc')
-rw-r--r--doc/bugs/git_annex_fork_bombs_on_gpg_file/comment_8_178fd4e4d6abbca192fcd6d592615fca._comment12
1 files changed, 12 insertions, 0 deletions
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.
+"""]]