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

Re: file: Access vs. Database stability

From: Greg Hudson <ghudson_at_MIT.EDU>
Date: 2004-04-04 18:38:08 CEST

On Sun, 2004-04-04 at 12:25, Jens-Uwe Mager wrote:
> From running a subversion server for quite a while (about over a year
> now) I get the feeling that for stability of the main server we
> absolutely have to ban all access via file urls and other non-http
> access methods. this in particular appears to affect viewcvs and similar
> which appears to have wedged our repository several times the last few
> days alone.

When the repository wedges, before recovering, do an "ls -l" of the db
directory. If you see a logfile with permissions which aren't writable
by the HTTP server, then you probably have a solvable permissions

The simplest way to ensure permissions safety is to make all access
methods use the same uid. If that's not desirable, you need to make
sure that they're all in the same group, that the db directory has the
g+s bit set (not necessary on the *BSDs, I believe, but it doesn't hurt
either), and that they all use an 002 or 007 umask so that the group
write bit is set on new logfiles.

> This appears to contradict the recommendation of the developers to
> use the direct svn API for utilities like viewcvs.

Orthogonal issue. You can get either local or remote access using
either the svn API or using command-line tools.

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sun Apr 4 18:38:30 2004

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

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