root wrote:
> Hi Tobias,
>
> Thanks for the response. I realize that what you
> indicate below is covered in the FAQ. However, I do
> not believe this to be the case. I am the lone
> administrator of this box and this repository. I can
> set up a brand new clean repository, and then from the
> client, do a checkout and the same thing occurs -- it
> hangs. I can guarantee that there are no other
> clients hitting the repository or local svn* processes
> hitting the repository at the same time the checkout
It's completely OK to have several clients accessing the repository at
the same time of course.
> is underway. Doing svnadmin recover does not seem to
> fix this problem.
I assume that you killed all svnserve:s, ran svnadmin recover, and that
it completed without error. We need to narrow this down a bit further.
Make sure that your repos is not a network drive, and that you do not
have a permission/umask problem.
Can you checkout using file://? If that works, can you run "svnserve -d"
on the server and access it via svn://?
You should also upgrade to the latest release (0.36) of course.
> What I am curious about -- is if it is possibly an SMP
> issue. Has anyone run svnserve on SMP boxes before?
I doubt that this is an SMP problem, but who can know for sure?
> What I see is that a single client doing a checkout
> connects via SSH one time and starts the svnserve
> process, then a second or so later connects via SSH
> again, and launches *another* svnserve process. Is
> this by design -- such that a single checkout requires
> 2 svnserve processes to be running? If so, is it at
Yes.
> all possible that there is deadlock between the two
> processes somewhere along the line that causes this
> hang?
Not likely.
/Tobias
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Jan 20 15:29:23 2004