From 2c5de4da2f734f118d308d81f4b1847f562a38ff Mon Sep 17 00:00:00 2001 From: openmedi Date: Wed, 11 May 2016 13:05:59 +0000 Subject: [PATCH] --- ...x_assitant_--stop__34___doesn__39__t_work_in_OSX_10.11.4.mdwn | 1 + 1 file changed, 1 insertion(+) create mode 100644 doc/forum/__34__git_annex_assitant_--stop__34___doesn__39__t_work_in_OSX_10.11.4.mdwn 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 0000000000..c57a50c358 --- /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.