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

AW: Subversion on a samba share

From: Alblas Huibert <Huibert.Alblas_at_metro-cc.de>
Date: 2004-09-15 10:44:58 CEST

> -----Ursprüngliche Nachricht-----
> Von: Enno Rehling [mailto:enno@despammed.com]
> Gesendet: Dienstag, 14. September 2004 16:07
> An: users@subversion.tigris.org
> Betreff: Re: Subversion on a samba share
>
>
> m christensen wrote:

[SNIP]

> We want the stuff they produced in our asset control, which
> is why we're
> making them use subversion. To the rest of us, that whole
> department is
> basically one user, because of the way they work. However, to
> samba, they
> are not just one user - and our network department is
> refusing to let them
> all be one samba user either.
>
> And poor me is stuck between all those conflicting sides, and
> the only thing
> that is technically in my way is that subversion is trying to
> make a file
> read-write and complains about not being allowed).

You can setup the samba share to use a specific user for file ownership on
the server side (same goes for group ownership).

You would create a "department" user on the server,
chown the share to the department user.

then in the share conf add:

"force user = department"

to the share conf.

Now all clients can connect with their normal user name,
but once they are connected, all users are the same user on the server
side....

Maybe this is a pointer in the right direction.

(but doing it the subversion way is still better, but you allready know that
:-)

The downside is that you lose the information who changed what file,
because all files are owned by the same owner.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Sep 15 11:26:25 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.