On Sun, 2005-07-17 at 21:15 -0500, Ben Collins-Sussman wrote:
> On Jul 17, 2005, at 9:02 PM, Christopher Ness wrote:
> > I might have misinterpreted the comment though,
>
> Yes you have.
That has been known to happen.
> We're only talking about clients accessing the
> repository directly via file:/// urls. Users who can do this are
> already free to open the database files in emacs and tweak them
> however they want. There's no "permissions" other than whatever the
> OS file permissions allow.
>
> svnserve and 'svn subcommand file:///' already share 80% of their
> code -- it's all in the libsvn_repos library. So that's why I'm
> trying to tie logging to libsvn_repos. The following processes all
> open repositories directly for reading/writing:
>
> mod_dav_svn
> svnserve
> svnlook
> svnadmin
> svn subcommand file:///
>
> And thus all of these processes should be able to log things when
> they use the repository.
So the proposal is not to make a swiss-army-knife-of-logging for SVN but
to fill the logging gap of local accesses which are not though apache.
Beautiful.
In your "rethunk" proposal post, shouldn't the log level of each
repository be stored in the .conf file as well as the file locations?
Will a restart be needed to re-read the conf files or will the getters
notice if a change occurs?
This could be done later since it could be encapsulated in the getter
code (or is the value cached in other processes?).
Chris
--
PGP Public Key: http://www.nesser.org/pgp-key/
22:31:39 up 1:33, 2 users, load average: 0.33, 0.28, 0.22
Received on Mon Jul 18 04:51:06 2005