On 22 Aug 2005, at 11:00 AM, Sander Cox wrote:
>
> On Aug 22, 2005, at 4:51 PM, Ben Collins-Sussman wrote:
>
> It has. But why on earth should it need to have access as it's
> group as well. I don't think that should be required. Maybe it is
> indeed a bug in the Apple file system but I truly think it is a
> subversion problem. As now I won't be able to mix usage of a
> file:/// repostiory which I could because I was a member of the
> group the dir was owned by. But that is something I don't really
> care about in my situation.
>
If the apache process was running as the user that owned the files,
then it wouldn't be a problem. What you're seeing would suggest that
whichever user owns the file is *not* the user as whom apache is
running. As a result, that user's ownership of the files is
irrelevant. However, the user owning the process attempting to
access the repository *is* (by what you've said) a member of the
subversion group (or whichever group now owns the files). This is
not a subversion bug; it is the way Unix-like permissions work. It
can be annoying, as it will sometimes result in weird errors if a
process is not running as who you think it is. If you can confirm
that the user owning the files does not have access to them with o+wr
set, then that's an Apple bug.
(incidentally, the best way to test such problems is often to su to
the user running the daemon process in question, i.e. sudo su apache,
and then attempt to access the files. You may need to give the user
a usable shell first, of course.)
Kevin Broderick
kbroderick@boltonvalley.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Aug 22 19:01:09 2005