From owner-freebsd-hubs@FreeBSD.ORG Tue Jun 10 06:31:14 2003 Return-Path: Delivered-To: freebsd-hubs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 65D6D37B401 for ; Tue, 10 Jun 2003 06:31:14 -0700 (PDT) Received: from kazi.fit.vutbr.cz (kazi.fit.vutbr.cz [147.229.8.12]) by mx1.FreeBSD.org (Postfix) with ESMTP id 032A043FDD for ; Tue, 10 Jun 2003 06:31:11 -0700 (PDT) (envelope-from cejkar@fit.vutbr.cz) Received: from kazi.fit.vutbr.cz (localhost [127.0.0.1]) by kazi.fit.vutbr.cz (8.12.9/8.12.9) with ESMTP id h5ADV6f6073176 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 10 Jun 2003 15:31:06 +0200 (CEST) Received: (from cejkar@localhost) by kazi.fit.vutbr.cz (8.12.9/8.12.5/Submit) id h5ADV5ut073175; Tue, 10 Jun 2003 15:31:05 +0200 (CEST) X-Authentication-Warning: kazi.fit.vutbr.cz: cejkar set sender to cejkar@fit.vutbr.cz using -f Date: Tue, 10 Jun 2003 15:31:05 +0200 From: Cejka Rudolf To: Ken Smith Message-ID: <20030610133105.GA66707@fit.vutbr.cz> References: <200306091636.h59GavDW043030@freefall.freebsd.org> <20030609195142.U581@korben.in.tern> <20030610064507.GA22617@fit.vutbr.cz> <7mn0gqh10y.wl@black.imgsrc.co.jp> <20030610070407.GA27204@fit.vutbr.cz> <7mllwah0ek.wl@black.imgsrc.co.jp> <20030610123733.GA28649@electra.cse.Buffalo.EDU> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030610123733.GA28649@electra.cse.Buffalo.EDU> User-Agent: Mutt/1.4.1i X-Scanned-By: MIMEDefang 2.16 (www . roaringpenguin . com / mimedefang) cc: freebsd-hubs@freebsd.org Subject: Re: [FreeBSD-Announce] FreeBSD 5.1 Released! X-BeenThere: freebsd-hubs@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: FreeBSD Distributions Hubs: mail sup ftp List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Jun 2003 13:31:14 -0000 Ken Smith wrote (2003/06/10): > > ftp-all same as FreeBSD-archive > > ... > > ftp-CERT FreeBSD/CERT/* > > Those all sound great, I've needed to sub-divide the rsync's myself Because of big memory needs or because of what? Memory is not such a big problem for cvsup. It seems to me that it is more about updating policy (when update and what - it would need short cvsup runs with releases/packages before checking cvsupped source trees...), than about prepared cvsup collections. Anybody can do similar splitting by use of -i flag/refuse file with cvsup, but everything needs maintenance, including cvsup collections. > May I add the suggestion of publicizing somewhere(s) exactly when the > ports get updated? If it's a routine weekly thing and more or less > always predictable putting that in a FAQ somewhere so that the mirror > sites only hammer on ftp-master for ports shortly after they were > supposed to change you might lower the load on ftp-master. I think that most critical is situation, when there are updated files on ftp-master and everybody wants to mirror them, so we do not need to solve situation, when anybody runs cvsup when there is nothing new for him. (???) > It seems like the ports updates are a roughly weekly thing but > I don't think I have ever seen anyone say that. Maybe starts can be known, but how to know, when these uploads end? > someone else with more rsync experience than me say whether having a > module that does this can be configured to work? I could be mistaken I'm not sure, if I understand correctly, but do you know about exclude option in rsyncd.conf directly in module specification? -- Rudolf Cejka http://www.fit.vutbr.cz/~cejkar Brno University of Technology, Faculty of Information Technology Bozetechova 2, 612 66 Brno, Czech Republic