Re: "witty subject line about logging feature"

On Thu, 2005-07-21 at 17:57 -0500, Ben Collins-Sussman wrote:
> A. Make it easy for any svn-related program to log messages to a
> common place -- not just server implementations, but *any*
> svn-related program. This makes it easier to find/manage logs,
> and rotate them.

I'm skeptical of this design goal, because normally logging only makes
sense when you're a server accepting requests from a client. Although
people might be interested in having a log of the svnadmin or svnlook
actions performed on a repository, I don't think that's any more worthy
of an application's attention than it would be for a program like "ls"
to log. Normally one uses process accounting or a similar facility to
accomplish that goal.

There are a few things that can go wrong with logging outside of
non-network requests:

  * The person running the program can circumvent the log by removing
the logging functionality from the code. So administrators might think
they're getting a complete log, but they aren't necessarily.

  * The person running the program may not have access to the log file,
which can result either in an incomplete log or gratuitous blocking of
the requested action.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Jul 22 02:22:11 2005