From owner-freebsd-hackers Mon Dec 18 10:45:36 2000 From owner-freebsd-hackers@FreeBSD.ORG Mon Dec 18 10:45:32 2000 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mothra.ecs.csus.edu (unknown [130.86.76.220]) by hub.freebsd.org (Postfix) with ESMTP id 75ABD37B400; Mon, 18 Dec 2000 10:45:32 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by mothra.ecs.csus.edu (8.11.1/8.11.1) with ESMTP id eBIKBQX52848; Mon, 18 Dec 2000 12:11:26 -0800 (PST) (envelope-from joseph@randomnetworks.com) Date: Mon, 18 Dec 2000 12:11:26 -0800 (PST) From: Joseph Scott X-Sender: scottj@mothra.ecs.csus.edu To: Dan Langille Cc: freebsd-hackers@FreeBSD.ORG, freebsd-ports@FreeBSD.ORG Subject: Re: processing incoming mail messages (FreshPorts 2) In-Reply-To: <200012181843.HAA18856@ducky.nz.freebsd.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 19 Dec 2000, Dan Langille wrote: # On 18 Dec 2000, at 12:03, Joseph Scott wrote: # # > Let's say, at a minimum you want the queue to run every 30 # > minutes. However, if there are a large number of commits in the queue, # > you may want to be able ramp up to queue processing as quickly as every 5 # > minutes. If there's only two items in the queue though, there's really no # > reason to run it every 5 minutes. # # I would rather process the queue as soon as a new message arrives. # Rather than have a message sit there. Hence, the "notification" of a # waiting process: OI! you got mail.... Then my original answer should have simply been, find a box that will host FreshPorts that can take the load of processing 5000 commit mails in a minute. :-) # # > Just some thoughts. # # appreciated. *********************************************************** * Joseph Scott The Office Of Water Programs * * joseph@randomnetworks.com joseph.scott@owp.csus.edu * *********************************************************** To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message