[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: Jens-Uwe Mager <jum_at_anubis.han.de>
Date: 2004-04-04 18:55:51 CEST

On Sun, Apr 04, 2004 at 12:38 -0400, Greg Hudson wrote:

> 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
> problem.

I know about the permission problem and have this solved using the
various setgid bits and running the major services all under one user
id. This problem appears to be painful, but solveable with some effort.

My problem appears to be the various utilities not exiting cleanly on
edge conditions or exceptions and thus leaving a wedged repository
behind.

> > 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.

Well, tools like viewcvs do not use this level of the abstraction, they
use the direct level which just uses the OS path name to a Berkeley DB
directory structure. Same with the mailer.py or any other useful tools,
there appear to be no examples for the level of abstraction you refer
to.

-- 
Jens-Uwe Mager	<pgp-mailto:F476EBC2>
---------------------------------------------------------------------
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:56:16 2004

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