Re: Somewhat corrupted repository: Berkeley DB Permissions errors on SVN 1.0.2

regarding the last line of your message -

Then why doesn't it work that way?

I would have no problem keeping the svnserve daemon running as user
'svn' and have clients connect to it. That's actually how I expected it
to run the first time I tried to bring it up. Here's me: "why isn't
svnserve -t working? svnserve -d does, i don't get it"

My problem is keeping an open port other than ssh. I was under the
impression that "tunnelling" was exactly that. So we return to the last
line of your message -- then why doesn't it work that way?

- paul

On May 26, 2004, at 3:51 PM, Ben Collins-Sussman wrote:

> There's no other way. svn+ssh:// isn't for the faint-hearted. There's
> no magic way to make it "work out of the box".
>
> CVS has similar problems out-of-the-box, assuming you have a bunch of
> system users all reading/writing RCS files. It's just the natural
> side-effect of a bunch of users trying to directly access database
> files.
>
> The only "clean solution" is to allow a *single* process to own and
> access the database.
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed May 26 23:36:19 2004