aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar openmedi <openmedi@web>2016-05-11 13:05:59 +0000
committerGravatar admin <admin@branchable.com>2016-05-11 13:05:59 +0000
commit98e44ab10b7db8f5b03d9397b2256d1ba9f4cdd8 (patch)
treee4c2588eec82939914b5daae304d729ce4ac7440
parent25cca2dd578fe5262352e4c1e5c5703e9048652e (diff)
-rw-r--r--doc/forum/__34__git_annex_assitant_--stop__34___doesn__39__t_work_in_OSX_10.11.4.mdwn1
1 files changed, 1 insertions, 0 deletions
diff --git a/doc/forum/__34__git_annex_assitant_--stop__34___doesn__39__t_work_in_OSX_10.11.4.mdwn b/doc/forum/__34__git_annex_assitant_--stop__34___doesn__39__t_work_in_OSX_10.11.4.mdwn
new file mode 100644
index 000000000..c57a50c35
--- /dev/null
+++ b/doc/forum/__34__git_annex_assitant_--stop__34___doesn__39__t_work_in_OSX_10.11.4.mdwn
@@ -0,0 +1 @@
+As the title suggests, stopping the assistant through the terminal doesn't work as expected and I had to kill the assitant by hand, which in turn means, that git annex has to repair the repo. A workaround seems to be to start the assistant through "git annex webapp" and use the shutdown daemon button in the webapp. Before this workaround does work, you have to "git annex assistant --autostop" and restart, so that launchctl won't keep the daemon running.