Subject: Re: lsof broken?
To: None <email@example.com>
From: Gary Duzan <firstname.lastname@example.org>
Date: 08/24/2003 18:59:54
I sorted out what the problem was. I had LOCKDEBUG enabled in
my kernel, which adds fields to struct lock and struct simplelock,
which must end up being part of struct kinfo_proc, since changing
the flag changes the struct size, which confuses kvm_getprocs().
Should I send-pr this? In general, kernel options shouldn't
break userland APIs, but LOCKDEBUG may be different enough not to
care. (For example, it doesn't show up in options(4).) Or maybe
kvm_getprocs() and/or the KERN_PROC sysctl API are just hopelessly
broken and lsof needs to use something else. Opinions?
Gary D. Duzan
In Message <200308161047.h7GAlNMM004949@capo.xnet.duzan.org> ,
email@example.com (Gary Duzan) wrote:
=>In Message <20030816094845.GB21197@myinternet.com.au> ,
=> Charlie Allom <firstname.lastname@example.org> wrote:
=>=>On Fri, Aug 15, 2003 at 04:11:30PM -0400, Gary Duzan wrote:
=>=>> Under current as of today (and previously under 1.6U) the pkgsrc
=>=>> lsof seems to be broken:
=>=>but have you tried the patched lsof in pkgsrc?
=>=>Check for your latest lsof Makefile version.
=>=># $NetBSD: Makefile,v 1.66 2003/08/13 13:24:15 atatat Exp $
=> Sorry, I left a couple things out. Yes, I did update pkgsrc
=>just before rebuilding lsof, which was after updating the kernel
=>and userland. Also, this is on i386.
=> Gary D. Duzan