From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Mailing-List: contact overseers-help@sources.redhat.com; run by ezmlm Received: (qmail 9114 invoked from network); 11 Jan 2003 23:53:01 -0000 Received: from unknown (HELO molenda.com) (192.220.74.81) by 209.249.29.67 with SMTP; 11 Jan 2003 23:53:01 -0000 Received: (qmail 62038 invoked by uid 19025); 11 Jan 2003 23:52:50 -0000 Date: Sat, 11 Jan 2003 23:53:00 -0000 From: Jason Molenda To: overseers@sources.redhat.com Subject: Re: cvs bytestats Message-ID: <20030111155250.A61626@molenda.com> References: <20030111220229.GA8763@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <20030111220229.GA8763@redhat.com>; from cgf@redhat.com on Sat, Jan 11, 2003 at 05:02:29PM -0500 X-SW-Source: 2003-q1/txt/msg00035.txt.bz2 On Sat, Jan 11, 2003 at 05:02:29PM -0500, Christopher Faylor wrote: > > I turned this off once before but I think Ian and Jason thought the data > was useful. Is this the kind of data that is useful when there is a > problem? Because I doubt that anyone is looking at this now. > I think it's useful for establishing trends and baselines. When the system starts to melt down - bandwidth is congested, disks fill up, processor maxes out - it's easy to look over the trends and see what is "normal" and how "normal" has changed over time. When you're looking for an acute problem, an anoncvs abuser, it's nice to have it running, but that's not an argument for necessarily leaving it running continuously. Those are the reasons I like having it, but I won't argue strenuously against disabling it if it causes some problem. I'd be willing to disable the message logging in cvs, as per Ian's suggestion, and install an updated binary. Jason