[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: libsvn_repos logging -- design problems

From: Ben Collins-Sussman <sussman_at_collab.net>
Date: 2005-07-15 17:40:48 CEST

On Jul 15, 2005, at 10:29 AM, Garrett Rooney wrote:
> Per-repos logfiles are specified in the repos config file. If
> there is no per-repos logfile, or the config file can't be parsed
> or something thus we can't find out about it anyway we fall back to
> a global log file. The global logfile is controlled by an svnserve
> command line option or an /etc/subversion/somethingorother
> directive, if no global logfile is set up then no logging happens,
> the same situation we have currently.

Yeah, but at the same time, it feels weirdly, overly complex to me.

I mean, imagine that a repository is correctly set up to have private
logfiles. Several confused users try accessing the wrong URL and get
rejected; these accesses end up in the global logs. But then the
users get the URL correct, and so their accesses are now going into
the repository's private logs. Hm.

When admins ask, "hey, where do I find svnserve's logs?", the answer
is now "look in two or more places, possibly".

It makes me wonder, honestly, if the 'errorlog' shouldn't be
completely global, all of the time, and can cover all debugging/error
messages for all repositories. We could decide that the *only* per-
repository logs are individual accesslogs.

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Jul 15 17:41:25 2005

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.