Nevermind my questions about selinux, this time around I found the right
way to disable it permanently, and I don't really care how to make it
work with svn, I don't think I need it.
For some reason, last time around this page was buried deep, this time
around it was near the top of my google:
http://www.redhat.com/docs/manuals/enterprise/RHEL-4-Manual/selinux-guide/rhlcommon-section-0068.html
BlackYoda wrote:
> Hi Patrick,
>
> Thanks for your response... Let me correct myself, I am indeed running
> apache 2.0.
> I installed the server so long ago I forgot that I installed apache 2.0.
>
> But since I received your response I started digging deeper, and
> discovered what was causing the problem.
> I am running FC3 - and selinux was enabled. Back when I was doing the
> original install I spent hours trying to figure out what was wrong,
> and somehow finally I stumbled across the fact that SELinux was casing
> those access errors, and so I disabled it, and everything worked. It
> probably wormed its way back to enabled on my system when I rebooted a
> while ago, and I have not used the repository much and mostly forgot
> about this issue.
>
> If anyone knows how to permanently disable selinux I think that would
> be superb.
> Or if anyone knows more about why selinux interferres with
> web_dav/Apache2/subversion and how I can make them play nice then that
> might be good too. But I'm not convinced that selinux is doing
> anything for me period and would like to kill it once and for all
> probably.
>
> But in the meantime, and in case anyone else has troubles with selinux
> this command disables it (apparently until you reboot):
>
> echo "0" > /selinux/enforce
>
> Thanks again, I'm back to happy source control land.
>
>
>
>
> Patrick Burleson wrote:
>
>>On Apr 11, 2005 8:54 PM, BlackYoda <BlackYoda@unholyplayground.com> wrote:
>>
>>
>>>Not sure what happened to make it stop...
>>>I had it all setup and everything was working. I'm using svn 1.1.2 with
>>>webdav on an apache 1.3 based server.
>>>
>>>
>>>
>>
>>Maybe this is too simple, but doesn't SVN require Apache 2.0 to be the
>>server if your going to use mod_svn? How would one even build it
>>against 1.3?
>>
>>Patrick
>>
>>
>>
>
Received on Tue Apr 12 07:45:18 2005