Dimitri Papadopoulos-Orfanos wrote:
> Hi,
>
>> I had a running, Subversion system through svnserve and WebSVN.
>> Today (and presumably yesterday) the WebSVN system started to
>> break--it wouldn't list files in the repos.
>
>
> What happened to the system between the moment it worked and the
> moment it didn't? Software upgrade? Change in configuration files?
>
>> Why would my 'nobody' account possibly be trying to access
>> /root/.subversion? Possibly because it's a httpd-started process?
>
>
> Right, the value of HOME is probably /root and the cause is probably
> that Apache is started as root. I don't know whether this is normal
> behavior or not though.
>
> Have a look at this:
> http://websvn.tigris.org/issues/show_bug.cgi?id=32
>
> Dimitri Papadopoulos
>
We have the same problem. Out server is Suse Enterprise Linux 9, and
every time the system management tool (yast2) finishes, it checks and
resets the permissions on a bunch of directories. This include /root/* ,
so websvn would run happily for days (or weeks), and then fail after I
used yast2.
This is configurable in the /etc/permissions* files.
Our apache server runs as wwwrun:www, and the wwwrun home directory is
certainly not /root, it is /var/lib/wwwrun, but websvn still needs
access to /root/.subversion
Haven't solved this one yet - we are just living with it so far.
Tony Butt
CEA Technologies
Canberra, Australia
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Oct 12 04:44:39 2005