On Wed, 26 Mar 2003, Mark Gulbrandsen wrote:
> Ben Collins-Sussman wrote:
> >
> > It's a permissions/umask problem. You've probably got different
> > processes using different umasks to read/write the db files, which
> > ends up blocking access for the next process.
> >
>
> Sure enough, fiddling with a few umask and permissions issues fixed this
> problem. Sorry to waste bandwidth. However, perhaps I can add something
> to all of this.
>
> I added a configure switch --with-suexec-umask=002 and recompiled
> apache. That didn't solve the problem, but I left it in (can someone
> confirm or deny that this has any relevance to the permissions problem?).
The suexec-umask will have no effect on Subversion at all. Suexec is for
running CGI scripts as a speceific user, and the suexec-umask flag just
tells Apache what the umask should be when running SuExec. But Subversion
is integrated into Apache as a module, which means that there is no CGI
cript, and thus SuExec isn't used.
Ryan
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Mar 27 15:54:57 2003