On Tue, Apr 14, 2009 at 12:06, Ben Kyrlach <bkyrlach_at_hobsons-us.com> wrote:
> Here’s my setup…
>
>
>
> Multiple users connect to SVN using SVN+SSH with a common key.
>
> The *nix machine hosting svnserve is using the authorized_keys file in each
> users $HOME/.ssh to launch svnserve when connecting with said key.
>
>
>
> Whenever a user makes a commit to the single FSFS repository there, the
> myrepository/db/current file has its ownership changed to the user. So, if I
> commit, the files ownership changes to bkyrlach.bkyrlach. Because the
> repository disallows any access at the “other” level, it essentially
> prevents any other users from committing to the repository. I’ve tried using
> sudo and or su in the authorized_keys file to run svnserve as root, but when
> I do this I get an error stating that I need a TTY in order to perform that
> action.
>
>
>
> Are my permissions set wrong perhaps? I had it set up so that everything
> myrepository under was owned by root.developers, and all of the people with
> svn access were in the developers group. Or is there a way to make svnserve
> not change ownership of that file?
You need to change the umask being set for those users. See the box at
the bottom of http://svnbook.red-bean.com/en/1.5/svn.serverconfig.multimethod.html
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=1712830
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-04-14 18:29:38 CEST