From owner-freebsd-hubs@FreeBSD.ORG Fri Oct 10 00:02:30 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 1E24716A4B3 for ; Fri, 10 Oct 2003 00:02:30 -0700 (PDT) Received: from smtp2.server.rpi.edu (smtp2.server.rpi.edu [128.113.2.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 12E3A43F93 for ; Fri, 10 Oct 2003 00:02:28 -0700 (PDT) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.netel.rpi.edu [128.113.24.47]) by smtp2.server.rpi.edu (8.12.10/8.12.9) with ESMTP id h9A72Q8j012254; Fri, 10 Oct 2003 03:02:26 -0400 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: <20031010060149.GA3707@math.uic.edu> References: <20031010060149.GA3707@math.uic.edu> Date: Fri, 10 Oct 2003 03:02:25 -0400 To: Vladimir V Egorin , freebsd-hubs@freebsd.org From: Garance A Drosihn Content-Type: text/plain; charset="us-ascii" ; format="flowed" X-Scanned-By: CanIt (www . canit . ca) Subject: Re: cvsup server operation 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: Fri, 10 Oct 2003 07:02:30 -0000 At 1:01 AM -0500 10/10/03, Vladimir V Egorin wrote: >We run updates (update.sh script) once per hour, however >there are some clients that request updates periodically >every 5-10 minutes, sometimes as often as every 2-3 minutes. >This doesn't make any sense to me; I agree it would not be good (or fair) for some cvs client to consistently do. However, I do occasionally do this from my cvsup client. I used to run cvsup once-per-week (by hand), because I knew I wasn't going to do anything during the week. Sometimes I'd skip a weekend or two, and by the time I did run it there might be a lot of files that needed to be updated. I found that lot of files would take a long time to update, and the longer that *my* cvsup run took, the more likely that some *new* updates would arrive on the cvsup-server while my update was going on. So, I would run cvsup again immediately after the first one was finished. Several times this tactic did save me from getting a partial update (where someone commits several files at once, but I only catch updates to half of those files). There might also be cases where multiple machines are on the other side of a NAT box from you. In that case, I assume what your server might see as multiple connections from one host might really be separate hosts making a connection. [that is just a guess on my part though] There are other situations where a single client might have a legitimate reason to run two or three times in a short amount of time. If you do decide to add something to throttle the clients that *constantly* contact the server every five minutes, it would nice (IMO) if it didn't penalize someone who only occasionally makes these repeated connections. -- Garance Alistair Drosehn = gad@gilead.netel.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu