From owner-freebsd-current@FreeBSD.ORG  Fri Aug 29 20:55:18 2003
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
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 8A62816A4BF; Fri, 29 Aug 2003 20:55:18 -0700 (PDT)
Received: from mailhub.yumyumyum.org (dsl092-171-091.wdc2.dsl.speakeasy.net
	[66.92.171.91])	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 4146A43FE3; Fri, 29 Aug 2003 20:55:15 -0700 (PDT)
	(envelope-from culverk@yumyumyum.org)
Received: by mailhub.yumyumyum.org (Postfix, from userid 1001)
	id 772977D7; Fri, 29 Aug 2003 23:55:01 -0400 (EDT)
Received: from localhost (localhost [127.0.0.1])
	by mailhub.yumyumyum.org (Postfix) with ESMTP
	id 727207D6; Fri, 29 Aug 2003 23:55:01 -0400 (EDT)
Date: Fri, 29 Aug 2003 23:55:01 -0400 (EDT)
From: Kenneth Culver <culverk@yumyumyum.org>
To: Robert Watson <rwatson@freebsd.org>
In-Reply-To: <Pine.NEB.3.96L.1030829165814.47993G-100000@fledge.watson.org>
Message-ID: <20030829235225.N25083@alpha.yumyumyum.org>
References: <Pine.NEB.3.96L.1030829165814.47993G-100000@fledge.watson.org>
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
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 30 Aug 2003 03:55:18 -0000

> 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?

I was running with just the kernel option, and nothing configured for it.
I can't think of what else the problem could be, when I recompiled the
kernel it just started working again, it might not have anything at all to
do with ACL's and more to do with the fact that I just recompiled it. One
of my other -CURRENT machines is working now as well after a recompile.
I'll do more testing to see if I can pinpoint the problem and I'll
probably have results by Tuesday (holiday weekend :-P )

Ken