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

Svnserve Logging (Yet again)

From: David Mahakian <tmoli42_at_gmx.net>
Date: 2006-06-27 19:52:53 CEST

So, logging.

As recommended by Garrett Rooney, I read through the dev@ archives and
read through the few hundred emails on logging, mostly from Ben
Collins-Sussman's implementation of logging for mod_dav_svn last year. I
want to summarize what was decided then and use that as the starting
point for more discussion.

For mod_dav_svn logging, the following was decided and implemented
(please please correct me if I'm wrong):

* Don't log errors, those are already logged in the apache error log
* Don't log low level actions (WebDAV stuff), those are already logged
in apache access log
* Log high level svn actions (checkout, commit, etc) to a new log file
(using CustomLog) that is shared between all repositories (i.e. it is
defined in the root (not under a Directory/Location) of the httpd.conf file)

Based on the above and the previous discussions of logging, this is my
new and improved svnserve logging description:

* Per repository (/ per svnserve instance) logging, configured in
svnserve.conf for that repository
* Log error and high level information, which may be configured to be
put into the same or different log files
* Log file format similar or identical to default of mod_dav_svn logging
(see http://svn.haxx.se/users/archive-2005-08/1448.shtml), and not
changeable (i.e. hard coded)
* Don't worry about log file maximum size (unless the apache logs do)
* If possible, use macros to also provide source file and line
information for errors if svnserve is built with --enable-maintainer-mode

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Jun 27 19:57:43 2006

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.