On 2019-04-08 16:38:37 +0200, Stefan Sperling wrote: > Since you have a way to reproduce the problem, even if unreliably, > you're in a position to help.
But it could take weeks... > If you don't try, we'll have to wait until someone else figures out where > the hang occurs or provides a clear and working reproduction recipe. > > Sorry, but bugs don't get fixed by magic ;) Well, I forgot, there's at least an issue with svnserve. I got that in the past, and could reproduce it: once I kill the svn client with Ctrl-C and kill the SSH master too, the sshd terminates, but svnserve is still running, and now has 1 as its PPID: UID PID PPID C STIME TTY TIME CMD vlefevre 48724 1 0 12:40 ? 00:00:00 svnserve -t If svnserve was waiting for something from sshd, it should at least have noticed that the connection is no longer there. lsof still shows: svnserve 48724 vlefevre cwd DIR 0,32 4096 110673531 /home/users/vlefevre (...:/forge_home) svnserve 48724 vlefevre rtd DIR 254,0 4096 2 / svnserve 48724 vlefevre txt REG 254,0 86256 9413 /usr/bin/svnserve svnserve 48724 vlefevre 0r FIFO 0,8 0t0 957950313 pipe svnserve 48724 vlefevre 1w FIFO 0,8 0t0 957950314 pipe svnserve 48724 vlefevre 2w FIFO 0,8 0t0 957950315 pipe svnserve 48724 vlefevre 3r CHR 1,9 0t0 7109 /dev/urandom BTW, is the permanent open of /dev/urandom normal? -- Vincent Lefèvre <vinc...@vinc17.net> - Web: <https://www.vinc17.net/> 100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/> Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
