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 8136 invoked from network); 11 Jan 2003 22:02:08 -0000 Received: from unknown (HELO redhat.com) (66.30.22.225) by 209.249.29.67 with SMTP; 11 Jan 2003 22:02:08 -0000 Received: by redhat.com (Postfix, from userid 201) id C2B271C115; Sat, 11 Jan 2003 17:02:29 -0500 (EST) Date: Sat, 11 Jan 2003 22:02:00 -0000 From: Christopher Faylor To: overseers@sources.redhat.com Subject: cvs bytestats Message-ID: <20030111220229.GA8763@redhat.com> Mail-Followup-To: overseers@sources.redhat.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.1i X-SW-Source: 2003-q1/txt/msg00033.txt.bz2 Do we *really* need to track all of the I/O activity for CVS? /var/log/syslog has thousands of messages like this: sourceware cvs: error setting KEEPALIVE: Socket operation on non-socket which is due to the fact that anoncvs is being run in a pipe so that we can track the amount of I/O performed by cvs. 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 noticed this while setting up cvs on the new system so I thought I'd revisit the decision. cgf