From owner-freebsd-questions@FreeBSD.ORG Wed Sep 29 23:27:17 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2C20416A4CE for ; Wed, 29 Sep 2004 23:27:17 +0000 (GMT) Received: from mail03.syd.optusnet.com.au (mail03.syd.optusnet.com.au [211.29.132.184]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5E01543D46 for ; Wed, 29 Sep 2004 23:27:16 +0000 (GMT) (envelope-from andrewr@uidaho.edu) Received: from c211-28-75-111.frank1.vic.optusnet.com.au (c211-28-75-111.frank1.vic.optusnet.com.au [211.28.75.111]) i8TNRErq029521 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Thu, 30 Sep 2004 09:27:15 +1000 Received: from c211-28-75-111.frank1.vic.optusnet.com.au (localhost [127.0.0.1])ESMTP id i8TNRtqU040685 for ; Thu, 30 Sep 2004 09:27:55 +1000 (EST) (envelope-from andrewr@uidaho.edu) Received: (from andrewr@localhost)id i8TNRtKS040684 for freebsd-questions@freebsd.org; Thu, 30 Sep 2004 09:27:55 +1000 (EST) (envelope-from andrewr@uidaho.edu) X-Authentication-Warning: c211-28-75-111.frank1.vic.optusnet.com.au: andrewr set sender to andrewr@uidaho.edu using -f Date: Thu, 30 Sep 2004 09:27:55 +1000 From: Andrew Robinson To: freebsd-questions@freebsd.org Message-ID: <20040929232755.GW5379@uidaho.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.1i Subject: Organizing the output of make etc. X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Sep 2004 23:27:17 -0000 Hi everyone, I'm administering my own little hobby system. Great fun. I notice that when I make targets, usually through portupgrade, a great deal of text flies by. Some of it is of obvious immediate use, such as this advice from Subversion: Make sure that: * all your svn users are members of a common group * this group is the group id of the db/ and locks/ subdirectories of your repository * the above subdirectories are writable by this group and some of it is not, unless the upgrade or installation fails, eg, the output from each compilation. What I'd like to know is: how do you more experienced types cope with this information flow? I'd like to use a little script that winnows out the useful advice from the recover-from-catastrophe-maybe advice, and then emails selections to root, with appropriate subject line, etc. Does anyone have a similar script,? If not I'll have a bash at writing one. If so, I'd love to use it. Thanks for any ideas! Andrew -- Andrew Robinson Ph: 208 885 7115 Department of Forest Resources Fa: 208 885 6226 University of Idaho E : andrewr@uidaho.edu PO Box 441133 W : http://www.uidaho.edu/~andrewr Moscow ID 83843 Or: http://www.biometrics.uidaho.edu No statement above necessarily represents my employer's opinion.