Loïc Joly <email@example.com> writes:
> 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 ?
You have read
> 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.
Uh, I guess you *haven't* read it. Go read it now :-)
> Last question : Is adding per directory access rights while using
> svnserve high on the priority list for subversion evolutions ?
I'm pretty sure a patch would be welcome.
To be more precise: I'd love to see it, and I think that others who
work on svnserve more than I do would also love to see it (or at the
very least would not object). But it's not high on anyone's priority
list right now, as far as I can tell.
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Mon Nov 15 23:09:25 2004