From owner-freebsd-current@FreeBSD.ORG Fri Sep 10 18:02:59 2010 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 127F7106566B for ; Fri, 10 Sep 2010 18:02:59 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from mail2.fluidhosting.com (mx21.fluidhosting.com [204.14.89.4]) by mx1.freebsd.org (Postfix) with ESMTP id AD2498FC14 for ; Fri, 10 Sep 2010 18:02:58 +0000 (UTC) Received: (qmail 9782 invoked by uid 399); 10 Sep 2010 18:02:57 -0000 Received: from localhost (HELO ?192.168.0.142?) (dougb@dougbarton.us@127.0.0.1) by localhost with ESMTPAM; 10 Sep 2010 18:02:57 -0000 X-Originating-IP: 127.0.0.1 X-Sender: dougb@dougbarton.us Message-ID: <4C8A72D2.1010507@FreeBSD.org> Date: Fri, 10 Sep 2010 11:02:58 -0700 From: Doug Barton Organization: http://SupersetSolutions.com/ User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.9) Gecko/20100825 Thunderbird/3.1.3 MIME-Version: 1.0 To: Mike Tancsa References: <201009081055.o88Atvu8050938@freebsd-current.sentex.ca> <20100908130700.GA53378@mail.hs.ntnu.edu.tw> <201009081439.o88EdHwh064108@lava.sentex.ca> <4C89663D.5050007@FreeBSD.org> <201009100754.o8A7sXLt078290@lava.sentex.ca> In-Reply-To: <201009100754.o8A7sXLt078290@lava.sentex.ca> X-Enigmail-Version: 1.1.1 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org Subject: Re: [head tinderbox] failure on amd64/amd64 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Sep 2010 18:02:59 -0000 On 9/10/2010 12:54 AM, Mike Tancsa wrote: > At 06:57 PM 9/9/2010, Doug Barton wrote: > >>> Normally they are pointed to a local mirror here at Sentex. However, >>> that server was having hardware problems which I think we have isolated >>> and resolved now. I will repoint this tinderbox to the local site again. >> >> The best way to handle this would be to have messages about csup >> failing to be directed only to those who are actually able to fix the >> problem. Assuming that the cvsup server is always going to work is >> contrary to both history and good system administration practices. :) >> >>> Perhaps as an interim measure a local procmail rule to filter out cvsup >>> failures from going to the list ? >> >> That's a particularly unhelpful response. Not only is it borderline >> rude to attempt to shift the responsibility for this to the users, >> it's a violation of the robustness principle. > > I meant "local procmail rule" as in local to the tinderboxes so that des > and myself and others who admin the boxes only get such messages. I > didnt want to make such changes without des' approval and was waiting > for his input... In that case I apologize for the misunderstanding. I've used procmail for many years on the receiving end but was not aware of the ability to use it in the manner you suggested. Doug -- ... and that's just a little bit of history repeating. -- Propellerheads Improve the effectiveness of your Internet presence with a domain name makeover! http://SupersetSolutions.com/