From owner-freebsd-current Sat Apr 8 14:31:32 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id OAA25777 for current-outgoing; Sat, 8 Apr 1995 14:31:32 -0700 Received: from trout.sri.MT.net (trout.sri.MT.net [204.182.243.12]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id OAA25766 for ; Sat, 8 Apr 1995 14:31:24 -0700 Received: (from nate@localhost) by trout.sri.MT.net (8.6.11/8.6.10) id PAA25993; Sat, 8 Apr 1995 15:35:22 -0600 Date: Sat, 8 Apr 1995 15:35:22 -0600 Message-Id: <199504082135.PAA25993@trout.sri.MT.net> To: "Rodney W. Grimes" Cc: nate@sneezy.sri.com, ache@astral.msk.su, freebsd-current@freefall.cdrom.com Subject: Re: SUP errors In-Reply-To: <199504081933.MAA15861@gndrsh.aac.dev.com> References: <199504081728.LAA23253@trout.sri.MT.net> <199504081933.MAA15861@gndrsh.aac.dev.com> Reply-To: nate@sneezy.sri.com (Nate Williams) From: nate@sneezy.sri.com (Nate Williams) Sender: current-owner@FreeBSD.org Precedence: bulk > > > SUP Receiving file TODO-2.1/CVS/Repository > > > > Fixed by the addition of 'omitany */CVS*' > > Humm... wonder if we made a mistake on that regex, should it not > be omitany */CVS/*??? I'll do some local testing and see if that > gets the same effect. I done like the idea that CVS* could match > CVSfiles or CVSfoobar, though the likely hood of names like that > ever coming up is near zero. I'll let you do your research. I just followed what was done before. > And grepping the sup config files on freefall makes me wonder about > the wasted CPU time for some of the others, that should never get > hit anyway: > > omitany *~ > omitany *.o > omitany */tags > > Nobody is suppose to muck around in the /usr/src or /usr/ports area, > so files by these names should never ever be created. It's better to be safe than sorry, and I suspect the extra overhead of these is so neglibible that it's not worth worrying about in terms of CPU hit. Nate