Received: (from majordom@localhost) by hyperreal.com (8.8.5/8.8.5) id IAA08766; Fri, 13 Jun 1997 08:33:59 -0700 (PDT) Received: from DECUS.Org (Topaz.DECUS.Org [192.67.173.1]) by hyperreal.com (8.8.5/8.8.5) with ESMTP id IAA08760 for ; Fri, 13 Jun 1997 08:33:55 -0700 (PDT) Received: from Lucy.DECUS.Org (lucy.process.com) by DECUS.Org (PMDF V4.2-13 #18511) id <01IK0TG7CO1C8WXJ2Z@DECUS.Org>; Fri, 13 Jun 1997 11:32:03 EDT Received: from master.process.com by Lucy.DECUS.Org; (5.65v3.2/1.1.8.2/16Sep96-0258PM) id AA12836; Fri, 13 Jun 1997 11:35:27 -0400 Date: Fri, 13 Jun 1997 11:31:03 -0400 From: coar@decus.org (Rodent of Unusual Size) Subject: Re: from-cvs To: New-HTTPd@apache.org, Coar@decus.org Message-id: <97061311310351@decus.org> X-VMS-To: NH X-VMS-Cc: COAR Content-transfer-encoding: 7BIT Sender: new-httpd-owner@apache.org Precedence: bulk Reply-To: new-httpd@apache.org >From the fingers of Brian Behlendorf flowed the following: > >If we were to set up cvsup, and give public read-only access to >it at leat, could we remove the "from-cvs" hierarchy? That appears to >contribute to a lot of FTP load, since it's changing daily and the >repository is huge. I don't know that cvsup would help so much. Erm, I suspect a significant part of the from-cvs HTTP load (*not* FTP) was from me; I forgot to nuke my cron job when I got direct access to the repository, so it's been faithfully fetching it regularly. Zapped. {blush} That was through HTTP with Lynx, though, not FTP. How many people actually grab the CVS tarballhow often, and via what schemes? Maybe it should be connexion-limited? #ken :-P}