Umask with rc_local

[Boris Boutillier <Bo...@lip6.fr>]

Hi all,

I'm using subversion for a university project, and for the moment i can 
only use local file:// access, as I'm not the Web administrator.

We are two people working on this project, with two different logins, and 
we both have a umask set to 022 ( which is the standard value : rw-r-r ).
The problem is that when we commit svn does'nt change this umask when 
dealing with files in the repository, particulary database access, and if 
it leads to the creation of a new log file or db file, the privileges on 
the file will be rw-r-r, and the second user won't be able to access the 
repository.

When looking at cvs, it changes in some way the umask as after a commit 
newly created file have ownership rw-rw-r which is the correct one for 
everyone in the group to acces the repository.

Is this a known bug and is there a workaround, I'm using subversion v 0.15 
( and didn't see this cubg correction in the changelog for 0.16).

Thanks all,

I'll take a look at the source code to see if it is something I can 
handle.

Boris


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org

Re: Umask with rc_local

[Nicholas Riley <nj...@uiuc.edu>]

On Thu, Dec 05, 2002 at 04:48:04PM +0100, Boris Boutillier wrote:
> I'm using subversion for a university project, and for the moment i can 
> only use local file:// access, as I'm not the Web administrator.

I can suggest a couple of solutions:

1. If you can run servers, then simply run Apache on a high-numbered port
as one of yourselves, using your own user database for authentication,
and use ra_dav exclusively.  This is definitely the easiest.

2. Assuming you're both in the same group, wrap svn in a script that
resets your umask to 007 or 002 before running it.  What I've done is
create a 'svn' group, and set the mode of the db directory to g+s so
files I create there are g+rw and group 'svn'.

> Is this a known bug and is there a workaround, I'm using subversion v 0.15 
> ( and didn't see this cubg correction in the changelog for 0.16).

Yes, it's a known bug, in that I mentioned it several months ago on
the list and nothing really became of it.  

-- 
=Nicholas Riley <nj...@uiuc.edu> | <http://www.uiuc.edu/ph/www/njriley>
        Pablo Research Group, Department of Computer Science and
  Medical Scholars Program, University of Illinois at Urbana-Champaign

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org