Re: Problems with file owner & permissions

Volker,

perhaps you don't enforce the correct umask for all users:
are you using svnwrap script?

less /usr/local/bin/svnwrap

# Generic wrapper for svn commands to enforce correct umask

#!/bin/sh

umask 002
cmdname=`basename $0`
exec /usr/bin/$cmdname "$@"

Put that in /usr/local/bin/svnwrap, make it excutable, and create links
for each command to the commands which must be wrapped:

cd /usr/local/sbin
ln -s /usr/local/bin/svnwrap svn
ln -s /usr/local/bin/svnwrap svnlook
ln -s /usr/local/bin/svnwrap svnadmin
ln -s /usr/local/bin/svnwrap svnserve

By the way: fsfs Filesystem is better than bdb (that's at least my
opinion), and keeps you safe from headaches :-)

Best regards
Arash

                                                                           
             Volker Poplawski
             <volker.poplawski
             @atrics.de> To
                                       users@subversion.tigris.org
             25.11.2004 16:56 cc
                                                                           
                                                                   Subject
                                       Problems with file owner &
                                       permissions
                                                                           
                                                                           
                                                                           
                                                                           
                                                                           
                                                                           

Hi all.

We have just switched from cvs a couple days ago.
svn works quite well (you have to get used to it) but one problem persists:

Whenever svn creates (or maybe berkeley db ) one of this db/log.000000xxx
files in the repository is created with wrong user id (user which does the
commit) and no write permission for the group. All svn clients barf after
that, reporting berkeley db errors.
The situation can be fixed by manual changing owner and group write
permissions as root on the repos, then running svnadmin recover and then
fixing permissions again.
svn will then continue to work until set_lg_max has been reached on the
active
file.

Our setup is as follows: We are using ssh for user authorization
(svn+ssh:/...) All the svn users have ssh logins on the repository machine.

The repository itself and all its files are owned by user 'svn' group
'users'
which is also the standard group for all the svn users.

It seems the whole problem is about svn not setting write-permission for
group when creating new files. cvs however, running on the same machine,
same
users, does.

Any suggestions?

Greetings
.....Volker

---------------------------------------------------------------------
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 Thu Nov 25 17:17:21 2004