bugs/leaves many stray processes on remote servergit-annexhttp://git-annex.branchable.com/bugs/leaves_many_stray_processes_on_remote_server/git-annexikiwiki2019-02-07T21:10:19Zcomment 1http://git-annex.branchable.com/bugs/leaves_many_stray_processes_on_remote_server/comment_1_b66015587ccd3ca81de52271979bd026/joey2019-02-07T20:06:20Z2019-02-07T19:58:58Z
<p>There is not much git-annex involved here; git receive-pack is being run in the
usual way by a git push, and git-annex-shell only forks off a git-shell to
handle it in the usual way.</p>
<p>If you change the ssh command to git-shell then git-annex would be out of
the picture, and so you could then tell if git-annex is somehow involved in
the problem at all on the server.</p>
<p>But I think that upgrading the client is the first step, or checking to
see if it has corresponding git processes that are keeping those git
receive-pack's going.</p>
<p>It could be that the client is losing connection with the server in a way
that doesn't cause the TCP connection to be closed on the server, and so it
waits around for whatever TCP timeout might eventually close it.</p>
comment 2http://git-annex.branchable.com/bugs/leaves_many_stray_processes_on_remote_server/comment_2_4f417206d5d83bd456c8e501ae272cba/anarcat2019-02-07T21:10:19Z2019-02-07T21:10:19Z
you'll notice that some of those processes have been hanging out there for days. i believe the TCP sockets are long gone, at least their parent SSH process are gone. this is why i related this to the "kill git-annex assistant on logout" - but since git-annex doesn't do setsid anymore (right?) I don't understand why those process could be left there without a parent... especially since that's on the server-side, which has a (relatively) up to date git-annex version...