On Sunday 31 December 2006 22:29, Andy Levy wrote:
> On 12/31/06, Bruno Costacurta <pubmb01@skynet.be> wrote:
> > On Sunday 31 December 2006 00:53, Matt Sickler wrote:
> > > no. only to $REPO/dav and $REPO/db does apache need write and read
> > >
> > > On 12/30/06, Konrad Rosenbaum <konrad@silmor.de> wrote:
> > > > On Saturday 30 December 2006 18:43, Bruno Costacurta wrote:
> > > > > My current settings for /usr/local/svn/repos/documents/ are:
> > > > > 0755
> > > > > user=bruno
> > > > > group=svnuser
> > > >
> > > > Does Apache run under the user "bruno"? If not: that is the problem.
> > > > Apache
> > > > needs write access to the whole repository.
> > > >
> > > >
> > > > Konrad
> >
> > Indeed I setup apache user in line with repository directories and it
> > works.
> >
> > Note: I still have some problems link to selinux which I disabled for
> > test. To resolv this I intend to simply move svn repositories to
> > /var/www/ to fit with http selinux securities.
>
> You aren't the first person to report clashes between Subversion and
> selinux policies. http://tinyurl.com/y96yh2 (google search on
> SVN-related mailing list archives)
>
Thanks for your attention.
Problems is now solved.
In fact when selinux is in mode enforcing the repository directory used by
apache need to be labelled with a context which httpd can write to.
By default this is the case under directory /var/www.
So I relocate subversion repository directory in a new directory created with
root and called /var/www/svn. Now svn is working with selinux enforcing.
Bye,
Bruno
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sun Dec 31 23:27:41 2006