Re: Corrupted Repository, Can't Recover

On Tue, 2004-05-25 at 10:45, C. Michael Pilato wrote:
> Andrew Wagner <awagner@uiuc.edu> writes:
>
> > For some reason I had to set the permissions of the entire repository
> > to 777 to get things working. I checked again in a corrupted
> > database, and except for one log file, everything is still set to
> > 777.
>
> Yeah, see, the problem with trying to fix stuff by setting permissions
> to 777 is that Berkeley is always creating new files -- those log
> files you saw one of -- and those new files are not gonna be 777. So,
> if your repos access is misconfigured such that you require 777 to get
> it to work, you can bank on it becoming busted again the minute a new
> logfile gets created.

FAQ:

http://subversion.tigris.org/project_faq.html#permissions

Chapter 6:

http://svnbook.red-bean.com/svnbook/ch06s05.html

[This is a recording.]

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed May 26 17:44:18 2004