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
is underway. Doing svnadmin recover does not seem to
fix this problem.
What I am curious about -- is if it is possibly an SMP
issue. Has anyone run svnserve on SMP boxes before?
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
all possible that there is deadlock between the two
processes somewhere along the line that causes this
--- Tobias Ringstrom <email@example.com> wrote:
> root wrote:
> > Hi,
> > I have an issue where a checkout of a repos simply
> > hangs.
> You need to run svnadmin recover on the repository.
> Make sure that there
> are no other processes running that are accessing
> the repository while
> you run recover.
> Problems such as this one occurs if a process dies
> while accessing the
> repository locally (svnserve, svnlook, svnadmin,
> file://, etc). The 0.36
> release has a number of fixes that make these
> processes shut down
> gracefully in cases where they were killed before
> (and thus causing
> repository hangs).
Do you Yahoo!?
Yahoo! Hotjobs: Enter the "Signing Bonus" Sweepstakes
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Tue Jan 20 14:55:22 2004