mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

followup

Browse source
This commit is contained in:
Joey Hess 2019-02-07 16:06:10 -04:00
parent 0c70b146eb
commit 27fe59fd3c
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
1 changed files with 21 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

21
doc/bugs/leaves_many_stray_processes_on_remote_server/comment_1_b66015587ccd3ca81de52271979bd026._comment Normal file
View file

@ -0,0 +1,21 @@
[[!comment format=mdwn
username="joey"
subject="""comment 1"""
date="2019-02-07T19:58:58Z"
content="""
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.
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.
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.
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.
"""]]