From owner-freebsd-hackers Mon Dec 18 10:43:17 2000 From owner-freebsd-hackers@FreeBSD.ORG Mon Dec 18 10:43:13 2000 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from ducky.nz.freebsd.org (ns1.unixathome.org [203.79.82.27]) by hub.freebsd.org (Postfix) with ESMTP id A845D37B400; Mon, 18 Dec 2000 10:43:12 -0800 (PST) Received: from wocker (wocker.int.nz.freebsd.org [192.168.0.99]) by ducky.nz.freebsd.org (8.9.3/8.9.3) with ESMTP id HAA18856; Tue, 19 Dec 2000 07:43:06 +1300 (NZDT) Message-Id: <200012181843.HAA18856@ducky.nz.freebsd.org> From: "Dan Langille" Organization: langille.org To: Joseph Scott Date: Tue, 19 Dec 2000 07:43:29 +1300 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Re: processing incoming mail messages (FreshPorts 2) Reply-To: dan@langille.org Cc: freebsd-hackers@FreeBSD.ORG, freebsd-ports@FreeBSD.ORG Priority: normal References: <200012181820.HAA18715@ducky.nz.freebsd.org> In-reply-to: X-mailer: Pegasus Mail for Win32 (v3.12c) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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.... > Just some thoughts. appreciated. -- Dan Langille The FreeBSD Diary - http://www.freebsddiary.org/ NZ ADSL - http://www.unixathome.org/adsl/ NZ Broadband - http://www.unixathome.org/broadband/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message