Ben Collins-Sussman wrote:
>
> 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?
I'm looking at the SVN repo log as belonging to the administrator
of the SVN repo, which may not be the same person that administers
the physical server (think Collab.net... :)
>> 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.
I'm not saying good-or-bad here, I am pointing out why I want
support for separate log files.
>> 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.
Right, that increases overhead (disk space, extra processing overhead
when doing reports, etc.), but it might also add confusion if you are
logging the physical disk location of the repo vs. the URL that was
used to access it.
>> 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.
OK.
--
______________________________________________________________________
Michael Sweet, Easy Software Products mike at easysw dot com
Internet Printing and Document Software http://www.easysw.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Aug 2 17:22:17 2005