On Feb 26, 2005, at 10:28 AM, Ben Collins-Sussman wrote:
>
> On Feb 26, 2005, at 6:43 AM, Daniel Kastenholz wrote:
>>
>> Any architecture- or style-related suggestions, remarks, hints... ?
>>
>
> I would very much like to see svnserve grow the equivalent of apache's
> "accesslog" and "errorlog". Many users have been asking for this. I
> don't imagine it would be tremendously difficult to do, but nobody's
> had time to do it yet.
>
> By the way, the svnserve protocol is documented here in the
> libsvn_ra_svn/ dir:
>
>
> http://svn.collab.net/repos/svn/trunk/subversion/libsvn_ra_svn/
> protocol
>
> ...so I'd use that -- as well as svn_ra.h -- as your guidelines to
> understanding what's going on in terms of client/server requests. I'd
> not only like to see a traffic counter being logged for each
> connection, but also each 'command' sent by the client being logged in
> an accesslog. And svnserve errors written to errorlog.
>
> If you have time to work on this, that's great. Be sure to read
> HACKING to understand how to submit patches for review. And be sure
> to work against svn's latest /trunk code, not some released tarball.
Would we really want to put the logging layer into svnserve? I don't
have a solution in mind ATM, but it *would* be nice to see some generic
mechanism that could be configured to log the various commands run
against a repository... maybe something like an access hook or
something?
-Fitz
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Feb 28 01:59:30 2005