> 2. mod_dav_svn learns to write "high level" logs, in addition to the
> existing low-level ones.
>
> --> a number of apache developers have told me about legitimate
> methods to write 'custom' svn messages into apache's
> accesslog.
>
>
> 3. nothing else writes logs.
>
> --> Logs aren't interesting or important (or trustworthy, or
> even necessarily complete) unless we're talking about
> server programs talking to clients over a network.
I don't like it. It means logging is specific to the way the repository
is served. Wouldn't it be better to make logging independent of that?
What about repositories which are used with several access methods?
Although I'm not a developer I'd like to propose a different approach:
Logs are tied to repositories. There would be an extra directory for
logs (or not, it could be just a file). It doesn't matter which access
method is used. As the logs are *per repository* admins with several
repositories can have their logs nicely classified.
Local file access is logged two! The argument about it having no
meaning... has no meaning! The "security" of the log system would be no
better than the security of the repository itself. Somebody who uses
file:// access doesn't care about security, and he still may want to see
how his repository is used.
All of this means logging to simple files. System logging is usually
useful for system events. Who would like to see each "svn up" as an
informational event in Windows' event viewer? In UNIX, the facilities
system is a broken concept, they are a random assigned number from a
small set!
Nobody has complained about Apache logging to its specific files. Simple
file-logging has several advantages: Logs are the same cross-platform,
and Subversion is heavily cross-platform. Tools can be written to
accesss them, process them and give statistics. Of course, it should
still be posible to configure the logging system to send logs above a
certain priority to the system log.
What do you think?
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Jul 28 01:11:22 2005