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

Re: file: Access vs. Database stability

From: Branko Čibej <brane_at_xbc.nu>
Date: 2004-04-05 07:43:11 CEST

Jens-Uwe Mager wrote:

>From running a subversion server for quite a while (about over a year
>now) I get the feeling that for stability of the main server we
>absolutely have to ban all access via file urls and other non-http
>access methods. this in particular appears to affect viewcvs and similar
>which appears to have wedged our repository several times the last few
>days alone.
I've had no problem combining file and http access and ViewCVS. But I
always use file aceess as the user Apache is running as, and we found a
whle ago that ViewCVS only causes problems if you enable source
colorizing but forget to install enscript.

>This appears to contradict the recommendation of the developers to use
>the direct svn API for utilities like viewcvs. I am getting the feeling
>that this recommendation is a reciepe for disaster, as you never get a
>stable repository as long as you allow develpment of utilities using the
>direct access methods. What do the others think about this conflict?
There is no conflict as long as you follow a few basic rules: Always
access the repository as the same user, and of course things don't go
too well when a tool crashes.

Brane Čibej   <brane_at_xbc.nu>   http://www.xbc.nu/brane/
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Apr 5 07:41:49 2004

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

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