On Feb 28, 2005, at 7:07 AM, Daniel Kastenholz wrote:
> Excuse me, but did I miss anyting? I haven't received any replies to
> this topic except for one from Ben Collins-Sussmann. Where does this
> one about the access hooks come from?
AFAICT, you've been explicitly cc'd on every mail in this thread.
Here's the whole thread:
http://svn.haxx.se/dev/archive-2005-02/1031.shtml
>
> As for the logging itself, I may not have a full overview yet, but I
> suppose the best starting point is syslogd.
> Logging to a syslogd as a first step would significiantly ease the
> other suggestions (e.g. Apache-style access_log and error_log),
> provided that the installed syslogd is not 90's itself and provides
> some sort of filtering mechanisms and output to different kinds of
> destinations, as is the case with syslog-ng, for example.
> I'm not sure, though, to what extent such a solution would work under
> Windows.
Ugh. We need to stay portable, and I'm dreading the thought of both
syslogd-specific Unix calls and win32-logging-API calls in our code.
Why not keep it simple? Why not just write data to our own private
logfiles, just like apache does? Is the problem really so complex that
we need to use OS-specific APIs?
> Also, I haven't yet decided whether to build this logging feature only
> into svnserve or make it accessible to the entire svn suite.
I think Karl Fogel said something like this in a different thread, and
I agree with him:
If apache didn't already exist as one of our servers, I'd say, "go
ahead and put logging functionality into the repository itself". But
because apache already exists and already does logging, I think makes
more sense to go for the low-hanging fruit of adding something similar
to svnserve.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Feb 28 14:43:11 2005