I'm not a resident expert, but the fact that you were having
troubles with locks and BDB
leads me to think someone was running svnadmin or some such as root or
of the user who "owns" the database. Not sure tho, as I use https so my
setup is different.
The one thing I know about fsfs is that you don't need write access to
read the DB, so
maybe that's why you haven't gotten lock problems since switching?
I think there still has to be some type of server process, even if you
use svn+ssh? Maybe
svnserv? At any rate there should be some logs on "the other side" you
might check to see
what commands are being sent to the "server" that are getting hung up.
For instance I found it helpful to check my httpd logs while setting up
Subversion to see
what urls and such were actually being sent back and forth. Sorry I
can't tell you where
to look for yours. Someone else around here would know the facts.
Joseph Moore wrote:
>Hi Everyone --
>We are having some problems using Subclipse with our new SVN server;
>any suggestions would be greatly appreciated.
>The major symptom is the Eclipse process for SVN actions hanging when
>using Subclipse for just about anything: checkout, update, commit,
>even simple repository exploring. Sometimes it works great,
>committing large transitions and lots of files, other times it gets
>stuck updating negligible changes, seemingly without any pattern.
>Eclipse is still functional but the SVN action attempted just spins
>and spins; the process can't be canceled and terminating Eclipse via
>the Task Manager is the only solution. No stack trace or other info
>appears in .metadata/.log.
>We're SVN newbies and have a generic SVN install, so hopefully there
>are some configuration tips and tricks we need to use to make things
>go a bit smoother.
>Our SVN server setup:
>- fsfs (file system) storage type. Berkeley DB (bdb) storage type
>kept having lock problems.
>- svn+ssh access. We don't run any actual server process running on
>the server since svn+ssh does not require or seem to use it.
>- everyone uses the same username and password
>- Server is Fedora Core 3 Linux and is about 10 feet away on the same network.
>- Configuration is vanilla: no hook scripts configured, nothing
>changed from the default.
>- access via svn+ssh
>- have used versions 0.9.37 and 0.9.101. We did get the NPE often
>with commits with 0.9.37, but I guess that bug was well known.
>To unsubscribe, e-mail: firstname.lastname@example.org
>For additional commands, e-mail: email@example.com
Received on Tue Dec 13 21:56:40 2005