From owner-freebsd-hubs@FreeBSD.ORG Thu Oct 9 23:01:50 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 EA05D16A4B3 for ; Thu, 9 Oct 2003 23:01:50 -0700 (PDT) Received: from cat.math.uic.edu (12-247-184-9.client.attbi.com [12.247.184.9]) by mx1.FreeBSD.org (Postfix) with SMTP id 038B443FBD for ; Thu, 9 Oct 2003 23:01:50 -0700 (PDT) (envelope-from vladimir@math.uic.edu) Received: (qmail 3775 invoked by uid 31415); 10 Oct 2003 06:01:49 -0000 Date: Fri, 10 Oct 2003 01:01:49 -0500 From: Vladimir V Egorin To: freebsd-hubs@freebsd.org Message-ID: <20031010060149.GA3707@math.uic.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.1i Subject: 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 06:01:51 -0000 After a long downtime, we've brought cvsup15.freebsd.org back to life. I've noticed however something odd in the logs. 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; this potentially could result in denial of updates to other clients if the queue is full of regular guests. I'd be interested in hearing whether other cvsup sites implement any access control mechanism that denies update to clients that have requested it very recently in the past, or shall I just pay no attention and let it be. Many thanks, -- Vladimir