I got interesting information from the sysadmin of the server: what the logs show is that a cron job reloads the unscd daemon every 10 minutes, a multiple of 10.
So, the hanging svnserve was started at about the same time as the reload of the unscd daemon. This was also the case when I had the problem in the past. And when I looked at the other "svnserve -t" processes that were started a long time ago on the machine, except for 2 users (which seemed to be particular as having many svnserve processes), the start times were also multiples of 10 minutes. Thus it seems to be a bug in svnserve (or a library it uses to connect to this daemon), which doesn't seem to handle failures correctly. -- 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)
