summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorGravatar https://me.yahoo.com/a/2grhJvAC049fJnvALDXek.6MRZMTlg--#eec89 <John@web>2012-10-20 05:31:45 +0000
committerGravatar admin <admin@branchable.com>2012-10-20 05:31:45 +0000
commitaeec5f1b7fc43f6be194cd38817b45a69bb70f5b (patch)
tree292d80b88c4cec3b701ba24ad50c315b5d091f3b /doc
parentf00a0ff995eced2bab828d03d69fadeba1ec5b24 (diff)
Diffstat (limited to 'doc')
-rw-r--r--doc/bugs/It_is_very_easy_to_turn_git-annex_into_a_zombie.mdwn23
1 files changed, 23 insertions, 0 deletions
diff --git a/doc/bugs/It_is_very_easy_to_turn_git-annex_into_a_zombie.mdwn b/doc/bugs/It_is_very_easy_to_turn_git-annex_into_a_zombie.mdwn
new file mode 100644
index 000000000..dd92591e6
--- /dev/null
+++ b/doc/bugs/It_is_very_easy_to_turn_git-annex_into_a_zombie.mdwn
@@ -0,0 +1,23 @@
+What steps will reproduce the problem?
+
+Run the git-annex assitant, and then "sudo kill" it.
+
+What is the expected output? What do you see instead?
+
+I expect it to die, instead I end up with:
+
+ 14604 ?? S 0:00.64 ga assistant
+ 14623 ?? Z 0:00.00 (git)
+ 14624 ?? Z 0:00.00 (git)
+ 14936 ?? Z 0:00.00 (git-annex)
+
+The only way to clear these zombies is to reboot. Perhaps there is some resource not being correctly terminated under exceptional conditions?
+
+Note that on OpenIndiana the problem is even more severe: Aborting git-annex at the wrong time leaves behind both zombie processes and lock files which cause the machine to suddenly halt if I try to access them in any way (via mv, rsync, etc)!
+
+What version of git-annex are you using? On what operating system?
+
+4d1e0c9 on OS X 10.8.2.
+
+Please provide any additional information below.
+