[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: a wrong chmod command rendered all my repositories unaccessible

From: Ryan Schmidt <subversion-2011a_at_ryandesign.com>
Date: Tue, 22 Mar 2011 15:04:45 -0500

On Mar 22, 2011, at 14:58, Walter Cazzola wrote:

> I'm administrating a SVN server for my lab with several
> repositories/projects accessed via SSL+DAV. The server runs on an old
> mandriva (2009) with subversion 1.5.2 and apache 2.2.9 with mod_dav,
> mod_ssl and mod_dav_svn installed. Repositories are separate directory
> associate to the project.
>
> A couple of days ago doing some cleaning on my server I've executed a
> «chmod 700 -R *» on the wrong directory (to be precise on /home/svn) with
> the result to render inaccessible the access to my repository from
> remote, as in the following case:
> >svn checkout https://url/svn/thales/trunk
> svn: access to 'https://url/svn/thales/trunk' forbidden
>
> I can't do update or commit as well. Before that catastrophic error
> everything was working well. I can't access neither from the command line
> nor from firefox.
>
> I've tried to change back the correct access rights but with no luck and
> also a «chmod 777 -R *» on the same directory didn't help. Also
> restarting apache doesn't help.
>
> What am I doing wrong? Attached to this message you find the current
> situation of one of my repositories with what I consider correct access
> rights.

The listings shown in your attachment show things that have not been chmod'ed 777.

Not sure about Mandriva, but on Mac OS X at least, the required syntax is "chmod -R 777 thing"; "chmod 777 -R thing" would show the error message "chmod: -R: No such file or directory".
Received on 2011-03-22 21:05:21 CET

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.