[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Conflict between webDav and svnserve ?

From: Loïc Joly <loic.actarus.joly_at_wanadoo.fr>
Date: 2004-11-15 21:01:58 CET

Hello,

I'm trying to set up a subversion repository. I first installed it with
an apache server, and it worked correctly, but very slowly (about 8s to
diff two normal sized files, on a local network). I then tried to
install svnserve to see if it worked faster. I installed it, and it
worked (significantly faster).

So, if everything works, where is the problem ? Well, after the second
installation, I tried to access the data through http:// once more, but
then it failed. And more than just failing, it corrupted the database
every time every time I tried. Access through svn:// of file:// still
works (well, after I correct the database through svnadmin recover of
course).

So, I would like to know if there are some specific issues when
accessing the database through both servers at the same time ?

By the way, I could notice some access rights stuff that might be
related to my problem. All my repository is in a folder owned by
dev:devgroup, apache is running under the username apache:apache (but
devgroup is a secondary user group for apache). Apache created (the
first time only, not during further tests) in my folder some log file
with user apache:apache, and I had to change the owner of those files
manually before svnadmin recover could work.

Last question : Is adding per directory access rights while using
svnserve high on the priority list for subversion evolutions ?

Best regards,

-- 
Loïc
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Nov 15 20:58:27 2004

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.