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

Re: Corrupted Repository, Can't Recover

From: C. Michael Pilato <cmpilato_at_collab.net>
Date: 2004-05-25 17:45:30 CEST

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.

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue May 25 17:46:13 2004

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.