From owner-freebsd-hubs Wed Dec 8 16:23:37 1999 Delivered-To: freebsd-hubs@freebsd.org Received: from ducky.nz.freebsd.org (chilled.unixathome.org [203.79.82.27]) by hub.freebsd.org (Postfix) with ESMTP id 5B58D15265 for ; Wed, 8 Dec 1999 16:23:34 -0800 (PST) (envelope-from dan@freebsddiary.org) Received: from wocker (wocker.int.nz.freebsd.org [192.168.0.99]) by ducky.nz.freebsd.org (8.9.3/8.9.3) with ESMTP id NAA68637 for ; Thu, 9 Dec 1999 13:23:31 +1300 (NZDT) Message-Id: <199912090023.NAA68637@ducky.nz.freebsd.org> From: "Dan Langille" Organization: The FreeBSD Diary To: freebsd-hubs@freebsd.org Date: Thu, 9 Dec 1999 13:23:31 +1300 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: traffic logs Reply-To: dan@freebsddiary.org X-mailer: Pegasus Mail for Win32 (v3.12a) Sender: owner-freebsd-hubs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Has anyone written anything to analyze the logs and determine the amount of traffic consumed by a cvsupd box? Preferably both the updates from master and the files served out to clients. thanks. -- Dan Langille - DVL Software Limited [I'm looking for more work] The FreeBSD Diary - http://www.freebsddiary.org/freebsd/ NZ FreeBSD User Group - http://www.nzfug.nz.freebsd.org/ The Racing System - http://www.racingsystem.com/racingsystem.htm unix @ home - http://www.unixathome.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hubs" in the body of the message