Date: Mon, 18 Dec 2000 11:22:58 -0800 (PST) From: Joseph Scott <joseph@randomnetworks.com> To: Dan Langille <dan@langille.org> Cc: freebsd-hackers@FreeBSD.ORG, freebsd-ports@FreeBSD.ORG Subject: Re: processing incoming mail messages (FreshPorts 2) Message-ID: <Pine.BSF.4.21.0012181119070.71411-100000@mothra.ecs.csus.edu> In-Reply-To: <200012161822.HAA03654@ducky.nz.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 17 Dec 2000, Dan Langille wrote: # Which list would be more appropriate for asking advice on designing a # mail processing strategy for FreshPorts 2 (i.e. processing all of cvs-all, # not just the ports)? # # I'm looking for recommendations and guidance on how to capture the # incoming messages and process them one at a time. As opposed to # starting a separate perl script for each message (which is the the # existing strategy and is usually fine, except when large numbers of # messages turn up in a short period of time). If you don't want to process a message the instant it comes in (via feeding it to a perl script or what ever) you'll need to setup some sort of queue, then have a cron job come through and process the queue. If the problem is load then another approach would be to heavily nice(1) the perl script the is launched when a commit mail comes in. *********************************************************** * 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.21.0012181119070.71411-100000>