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

Re: libsvn_repos logging -- design problems

From: Ben Collins-Sussman <sussman_at_collab.net>
Date: 2005-07-15 19:49:04 CEST

On Jul 15, 2005, at 11:36 AM, Ben Collins-Sussman wrote:

>
> Are we talking about tossing *all* mention of errorlog (and
> loglevel) in the public API, and just make the API talk about per-
> repos accesslog? (In which case, mod_dav_svn continues logging
> errors to apache's errorlog, and svnserve grows some private
> errorlog/loglevel ability that goes into /etc/subversion/...)
>
> Or, should we still have a notion of a 'shared' errorlog in /etc/
> subversion, usable via a public API? (The public API just wouldn't
> make use of svn_repos_t; it would be more generically available to
> all servers.)
>

<sussman> do you think it's still worthwhile having a generic
'global' errorlog API, one which servers can share, and has nothing
to do with svn_repos_t?

<ghudson> It never seemed very important to me.

<ghudson> I'll note that if mod_dav_svn wants to log more informative
errors, it can do so to the Apache log

----
So perhaps I'll go for the simpler option:  let errorlogging (and  
'loglevels') be something completely internal to the server.  Apache  
already has it, and someone will need to implement it for svnserve.   
(Maybe me, maybe someone else.)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Jul 15 19:49:48 2005

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