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

Re: logging: are we there yet?

From: Ben Collins-Sussman <sussman_at_collab.net>
Date: 2005-08-02 16:07:26 CEST

On Aug 1, 2005, at 7:03 PM, Michael Sweet wrote:

> 1. Different people manage different repos, and you might not
> want everyone to have access to every project's log data.

? There's only one server administrator, isn't there? Since when are
users able to examine the repository database directly?

> 2. Some repos are more active than others, and so you might want
> to rotate/process/audit a busy project's log file more often
> than a slow project.
> 3. By putting everything in one file, you force the data to be
> separated N times instead of 1 time.

I'm not sure I understand why these are good or bad things.

> 4. By putting everything in one file, you force the server to
> know some notion of where the repository is located, i.e.
> if someone checks out http://server/project/foo/trunk,
> mod_svn needs to log the full repository path instead of
> the relative path within the repo.

The server always knows where each repository is located; it
couldn't open the repository otherwise. :-) You're right, with a
shared logfile, the names of the repositories would have to be
logged, so that we can tell the logs apart, that's a given.

> So, if I may so humbly request that at least mod_svn support
> logging to separate files - Apache already supports that...

We're not planning on making any changes to the way apache/
mod_dav_svn's logging mechanism. We're only going to make it log
*more* things.

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Aug 2 16:09:51 2005

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.