Strange behavior svnserve.conf auth-access

[Eric Berry <el...@gmail.com>]

Hello,
    One of our Sys-Admins here set up a SVN repository for us to test with
(We are trying to convert over from cvs to svn). His svnserve.conf file had
these entries:
########
[general]

anon-access = none
auth-access = write,read

password-db = passwd
########

After some discussion with the guys from the Subclipse project we realized
that the auth-access needed to be set to just "write" not "write,read".

Before making the change however, we noticed that we were not able to
connect to the repository at all. It was acting as if anon-access was set to
"none" (which it was) and auth-access was also set to "none". The Systems
administrator did not receive any notification telling him that he had made
a mistake, and I'm not sure where the log files are. I checked /var/logs and
didn't see anything there.

Is this a predicted behavior, and where does svnserve log to so we can avoid
future mistakes?

Thanks for any help,
Eric

--
Infinite Loop: Someone included an include that included the include?

Re: Strange behavior svnserve.conf auth-access

[Nico Kadel-Garcia <nk...@comcast.net>]

I've given up on svnserve.conf for now: I find the svnperms.py and svnperms.conf add-ons to be much more flexible and configurable with the distinct concepts of "add", "delete", and "update".
  ----- Original Message ----- 
  From: Eric Berry 
  To: users@subversion.tigris.org 
  Sent: Tuesday, April 11, 2006 6:25 PM
  Subject: Strange behavior svnserve.conf auth-access


  Hello,
      One of our Sys-Admins here set up a SVN repository for us to test with (We are trying to convert over from cvs to svn). His svnserve.conf file had these entries:
  ########
  [general]
   
  anon-access = none 
  auth-access = write,read
   
  password-db = passwd
  ########

  After some discussion with the guys from the Subclipse project we realized that the auth-access needed to be set to just "write" not "write,read". 

  Before making the change however, we noticed that we were not able to connect to the repository at all. It was acting as if anon-access was set to "none" (which it was) and auth-access was also set to "none". The Systems administrator did not receive any notification telling him that he had made a mistake, and I'm not sure where the log files are. I checked /var/logs and didn't see anything there. 

  Is this a predicted behavior, and where does svnserve log to so we can avoid future mistakes?

  Thanks for any help,
  Eric

  -- 
  Infinite Loop: Someone included an include that included the include?