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

Re: Problem with svn+ssh

From: Todd A. Jacobs <nospam_at_codegnome.org>
Date: 2004-02-02 09:53:21 CET

On Sun, 1 Feb 2004, Ben Collins-Sussman wrote:

> authenticated to ssh as yourself.) So unless you're authenticating to
> ssh as user 'subversion', of course your 'svnserve' process doesn't have
> read-write access to the db files.

The problem in this case turned out to be the lack of o+rx permissions on
the subversion repository. Apparently, even though I had group read/write
permissions on all the database files, I needed o+rx on the parent
directory in order to for svnserve to work properly. I'm still not 100%
sure why that is so, but it seems to have solved issue for me.

> Have you read the 'svnserve' documentation in chapter 6 of the book?
> It explains this stuff in detail.

It could use a bit more detail. Overall, the documentation is quite good,
although a few more successful recipes for non-WebDAV configurations would
be very helpful. Granted, there are some subtle interactions, but a
known-good "test" configuration with listed permissions and so forth would
have saved me quite a bit of trial and error. :)

Todd's "Customer Disservice Hall of Shame" currently contains:
    - Charter Communications: Mislead their customers about service
      levels, block normal Internet connectivity, and exhibit excessive
    - AT&T: Honoring the "checks" they send out to entice you to switch
      long-distance providers is apparently optional.
    - eFax: Receive (not send) 20 pages of *unsolicited* faxes, and lose
      your account.
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Feb 2 09:53:44 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.