We had the problem only via svn protocol, svn+ssh / http both works.
However, I guess we experienced something different than the timeout problem described in #3347 - in our case svn server and client are on the same switch in a private network without disconnects, and still both block in read().
However, I guess a reasonable timeout should solve this - or at least fail-fast.
> -----Original Message-----
> From: Stefan Sperling [mailto:stsp_at_elego.de]
> Sent: Thursday, May 28, 2009 11:50 PM
> To: Moritz Möller
> Cc: Erik Huelsmann; users_at_subversion.tigris.org
> Subject: Re: svn update stuck in read() - matching svnserve process
> also in read()
>
> On Wed, Apr 01, 2009 at 09:50:01PM +0200, Moritz Möller wrote:
> > Hi,
> >
> > rngd is running on the machine and
> > /proc/sys/kernel/random/entropy_avail is monitored. And if I'm not
> > completely wrong the svn client is single threaded and the blocking
> > call is on the network connection, and the server is multithreaded
> but
> > in case of missing random entropy it should either wait in a futex or
> > wait on a read() on /dev/*random.
> >
> > To me it looks more like a protocol error. I will try to see if it
> > also happens with svn+ssh or http protocols.
>
> Moritz,
>
> what did you find out about the other protocols?
>
> I am asking because I have just made a patch to fix the same
> or a related problem over svn://, but would like to know if other
> protocols also suffer similar problems.
>
> See http://subversion.tigris.org/issues/show_bug.cgi?id=3347
>
> Thanks,
> Stefan
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2356679
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-05-29 09:12:47 CEST