logging: drill down a bit

Let me drill down a wee bit on the proposal we're pushing.

The main point of the proposal is not to reinvent logging, but rather
to re-use existing logging facilities. In the case of svnserve, it
should be a "good citizen" by writing to either the unix syslogd or to
the windows event subsystem. In the case of mod_dav_svn, it is a
"good citizen" by writing to apache's existing accesslog.

But I'm also hearing some people ask for more flexibility here:

   1. People may want to specify that svn-related messages be put into a
      separate logfile. (In other words, don't just dump svnserve
      messages into /var/log/messages, and don't just dump mod_dav_svn
      messages into apache's accesslog.)

   2. People may want to specify that per-repository messages be
      written to per-repository logfiles.

What I'm wondering is: do the existing logging subsystems provide this
sort of flexibility? Assuming that the messages being sent to
{syslogd, windows event system, apache logging system} are
sufficiently detailed, can these three systems be jiggered to do the
sort of filtering described above? If so, then I think everyone can
be happy.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Aug 2 23:39:52 2005