Although they all belong to the same group, and you may even use
chmod g+s on the directories to force that to remain so, you *also* need
to make sure that different users (you, the apache user) have a
group-write umask (002 instead of the usual 022) so that files you
create (new db log files, say) are also writable by the other users.
There are various methods for doing that.
Cheers...
Bruce
Harrison B. Caudill wrote:
> On Thu, 4 Mar 2004, Ben Collins-Sussman wrote:
>
>
>>On Thu, 2004-03-04 at 00:21, Harrison B. Caudill wrote:
>>
>>>I have the mod_dav_svn plugin up and functioning 'properly', but It seems
>>>to be causing a problem:
>>>
>>>every commit or other commit, it will require an svnadmin recover.
>>>
>>>I'm afraid I can't be very rigorous about reproduction of the error, If I
>>>figure that part out I'll let you know. I'm just hoping that someone has
>>>seen this before.
>>
>>Yes, it usually means permissions are messed up. Is *anything* other
>>than apache ever accessing the repository? Perhaps svnserve, or a
>>client using file:///? Or svnlook?
>>
>>When a repository wedges, it's almost always because some process didn't
>>cleanly detach from the database. Perhaps apache is segfaulting, or
>>you're hitting Control-C when accessing via svnlook or file:/// ?
>
>
> I havn't Ctrl-C'd during a commit, co, or anything else, but I have
> probably stopped it while viewing it online. I *do* access the same
> repository via file:// as well as svn+ssh://. Right now they all belong
> to the svn group, the www user is a part of the svn group, and I have done
> chmod -R g+rwX * on the repositories. I've even played w/ accessing via
> the web while i'm in the middle of a commit process and found it pretty
> thread safe, which is one reason this confuses me so much.
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Mar 4 16:01:38 2004