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

Re: Sharing SVN-Repository between Linux/x86 and WinNT

From: Ulrich Eckhardt <eckhardt_at_satorlaser.com>
Date: 2004-02-25 18:12:28 CET

(I'd have replied to the original message, but it seems it wasn't sent to
users@s.t.o. )

On Mon, 2003-12-29 at 18:33, Folker Schamel wrote:
> In our company, we first set up a linux svn+ssh:// server,
> accessing both from Linux and windows clients via ssh.
> Result:
> We had to run recovery all the time, several times per day.
> (Maybe we all are too hectic and hit Ctrl-C all the time...)

Can you describe a bit further what happened? Have you found a real reason for
the problems?

> I suppose svn+ssh and file:// are very similar and have
> similar problems.
> From this perspective, I understand Aaron's / Philmann (?)
> complainment about quality, and I agree completely
> with him that using Subversion with file:// is NOT
> in a usable state yet.

I'd assume that all accesses finally boil down to a file:// or similar access,
so the problem must be somewhere in between. Failure to lock the DB on an NFS
mount or a defective BDB version come to mind.

> Then - especially since all the Subversion docu clearly
> says that the recommended way is to use http://
> - we set up Subversion in this way (Apache under Suse Linux).
> Result: Perfect.

I don't see that the docs say so, Apache and svnserve are both distinct ways
to setup a server. Both have limits and advantages, but I don't see either
preferred. I personally prefer svnserve because Apache is a big blob of
software that I'm not even close to understanding.

I'd like to hear more about problems, since I'm also currently deploying a
first installation for >1 user.



To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Feb 25 18:12:11 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.