2 ports broken after gcc import
rwatson at freebsd.org
Sat Aug 30 07:45:40 PDT 2003
On Fri, 29 Aug 2003, Kenneth Culver wrote:
> > 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 )
I just built a fresh nmap on my -current box and it appears to work fine
for me, as did the older nmap. So I guess that leaves me firmly in the
"unable to reproduce" camp. I have noticed that, on my wi0 boxes, I tend
to get a fair number of ENOBUFS errors when nmaping, but that appears to
be unrelated to the presence of UFS_ACL in the kernel.
Are your different boxes using the same type of network interface? Do you
rely on routed or use static routes? If you tcpdump the interface, do any
nmap packets get out -- for example, the initial ping it performs before
scanning a host, or none?
Have a good holiday weekend :-).
Robert N M Watson FreeBSD Core Team, TrustedBSD Projects
robert at fledge.watson.org Network Associates Laboratories
More information about the freebsd-ports