On Jun 17, 2004, at 12:13 PM, Ulrich Eckhardt wrote:
> paul. wrote:
>> I'm having a permissions problem with an svn+ssh:// access method on a
>> repository hosted on a gentoo linux server. Since gentoo's portage
>> installs at /usr/bin/svnserve, i had to make /bin/svnserve be:
>> #!/bin/sh
>> umask 002
>> /usr/bin/svnserve "$@"
> That conclusion is wrong. Other systems install it in the same
> location and it
> works without a script in a different (and IMHO inapropriate) place.
What is the conclusion / assumption that I am making that is wrong?
That portage installs to /usr/bin/svnserve? It does.
That /bin is earlier in the $PATH? It is.
I don't see any other assumptions, so it must be something i don't even
realize i'm assuming.
>> I'm still getting db files created with permissions 755 (ie, umask
>> 022). This would seem to contradict the fundamental operations of a
>> unix permissions system.
> Hmmm, maybe it's just a PATH issue? If /usr/bin comes before /bin,
> some other
> user might find the original executable instead of your wrapper.
it's not a PATH issue, i've checked all the users, their PATH is
/bin:/usr/bin:....
Does svn+ssh:// explicitly call % /usr/bin/svnserve, or does it just
call % svnserve ? That could be the difference, but on FreeBSD it
worked as % svnserve -- thus calling the wrapper earlier in the path.
Maybe I'm assuming that it does that, but maybe it changed recently, so
that it calls /usr/bin/svnserve explicitly?
Regardless, /bin is earlier, and the wrapper is not being called. I
simply need to know what I can do to change that situation.
> Uli
- paul
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Jun 17 20:26:20 2004