From owner-freebsd-current@FreeBSD.ORG Fri Aug 29 14:00:06 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C066616A4BF; Fri, 29 Aug 2003 14:00:06 -0700 (PDT) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id BD8A543FDF; Fri, 29 Aug 2003 14:00:04 -0700 (PDT) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (localhost [127.0.0.1]) by fledge.watson.org (8.12.9/8.12.9) with ESMTP id h7TKxYrO049750; Fri, 29 Aug 2003 16:59:34 -0400 (EDT) (envelope-from robert@fledge.watson.org) Received: from localhost (robert@localhost)h7TKxYjN049747; Fri, 29 Aug 2003 16:59:34 -0400 (EDT) Date: Fri, 29 Aug 2003 16:59:34 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org To: Kenneth Culver In-Reply-To: <20030829161053.E22818@alpha.yumyumyum.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-current@freebsd.org cc: freebsd-ports@freebsd.org Subject: Re: 2 ports broken after gcc import X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 29 Aug 2003 21:00:06 -0000 On Fri, 29 Aug 2003, Kenneth Culver wrote: > > Just for more info, when was the last time you updated your /etc? on my > > 4th -CURRENT machine, with the same compiler etc... I havn't updated my > > /etc/ since June 1, and that machine works, the other 3 have been updated > > very recently, like within the last few weeks, and they're all broken. So > > I guess it's not a compiler issue, but some kind of configuration issue. I > > can't think of what the problem could be though. > > > OK, checked over my kernel configurations and found that ACL's were in my > kernel configuration. I took that option out and things are working again. > I have no idea how ACL's could've caused what I was seeing, but everything > is working now. Thanks for your help. Bizarre. I use ACLs in my kernel daily, and I use nmap almost daily, and haven't seen this. If you re-add ACLs with a fresh kernel build, does the problem come back? Could you look at ktraces of nmap with and without ACLs and see what causes it? Do you have ACLs enabled on any file systems, or are you just running with the kernel option? Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Network Associates Laboratories