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

Re: Svnserve Logging (Yet again)

From: Madan U Sreenivasan <madan_at_collab.net>
Date: 2006-06-29 09:03:34 CEST

On Wed, 28 Jun 2006 19:26:50 +0530, Michael Sinz <Michael.Sinz@sinz.org>

> On 6/28/06, Peter Samuelson <peter@p12n.org> wrote:
>> [Madan U Sreenivasan]
>> > Or how about generating a log-file name by appending the date/time
>> > stamp, and once it reaches a specific (configured) size, open a new
>> > file with another generated name?
>> That's pretty nonstandard.
>> Log file rotation is a solved problem, by time interval or by file size
>> or both, compressing and deleting old log files in configurable ways.
>> There's no need for each app to reinvent _any_ of it.
> Absolutely! Even more so, the whole file writing thing is "solved"
> too - by using the system logging facilities (syslog or the Windows
> logging system)
> There are major reasons to use the system logging support, such as
> centralized logging, configuration control via the standard logging
> tools, support/integration with various system monitoring tools, and,
> of course, the whole log file rotation, naming, archiving, etc.
> BTW - Part of the reason for centralized logging is the fact that in
> any organization of a reasonable size you end up with many machines
> and don't want to have to connect to each to monitor or diagnose a
> problem. Plus, there is the security issue of wanting to have the
> logs on a separate machine (and secure) such that it is that much
> harder for someone to try to cover their tracks. (Done right, it is
> nearly impossible.) SOX and other laws now demand more corporate
> responsibility and auditability in a number of these areas.


hmmm, I understand. Thanks Peter, Mike.


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Jun 29 08:33:21 2006

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