Ben Collins-Sussman wrote:
> 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.
You can create custom event logs on Windows 2000 and later. I think you
can even configure the logging system to use this log for a particular
event log without changing the code that produces the logs. The only
thing that you have to do is to register your app as a distinct event
source (that has to be done in the code), the rest can be tweaked in the
Registry.
The really serious catch is that you can't configure the logging system
to write logs to a file or to stdout/err, which IIRC syslog can do.
-- Brane
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Aug 3 00:39:57 2005