You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Markus Leuthold <ku...@forum.titlis.org> on 2008/02/20 14:45:22 UTC

consecutive access via svn:// stalls

Hello

I access a subversion repository via svn://, e.g
$ svn://server/repo log
After the third consecutive execution of the command above, the 
execution is stalled for like a minute. When I wait for a few minutes, 
everything is ok again and feels snappy. It looks like I triggered a 
timeout. If I execute the same command via file:// protocol, I don't 
experience these timeouts.

I found a workaround for this problem: In svnserve.conf, I set 
anon-access=none. If I change this value to anon-access=read, I don't 
experience timeouts after consecutive access of svn://server anymore.

I use:
gentoo linux
subversion 1.4.4

whats going on here? bug?

Kusi







---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: consecutive access via svn:// stalls

Posted by Erik Huelsmann <eh...@gmail.com>.
On Wed, Feb 20, 2008 at 3:45 PM, Markus Leuthold <ku...@forum.titlis.org> wrote:
> Hello
>
>  I access a subversion repository via svn://, e.g
>  $ svn://server/repo log
>  After the third consecutive execution of the command above, the
>  execution is stalled for like a minute. When I wait for a few minutes,
>  everything is ok again and feels snappy. It looks like I triggered a
>  timeout. If I execute the same command via file:// protocol, I don't
>  experience these timeouts.
>
>  I found a workaround for this problem: In svnserve.conf, I set
>  anon-access=none. If I change this value to anon-access=read, I don't
>  experience timeouts after consecutive access of svn://server anymore.
>
>  I use:
>  gentoo linux
>  subversion 1.4.4
>
>  whats going on here? bug?

Probably not. I think you're experiencing lack of entropy: the
svnserve protocol uses entropy (reads from /dev/random) for its
authentication with CRAM-MD5. When there's not enough entropy in the
system, the system stalls until there is (this is a property of
/dev/random). When you skip authentication, ofcourse you skip the step
of drawing entropy, preventing any stalls.

HTH,


Erik.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org