From owner-freebsd-current Thu Oct 28 4:28:41 1999 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (wandering-wizard.cybercity.dk [212.242.43.150]) by hub.freebsd.org (Postfix) with ESMTP id 9AAB514D74 for ; Thu, 28 Oct 1999 04:28:37 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id JAA00314; Thu, 28 Oct 1999 09:09:54 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Chuck Robey Cc: current@freebsd.org Subject: Re: lsof + namecache In-reply-to: Your message of "Wed, 27 Oct 1999 10:03:24 EDT." Date: Thu, 28 Oct 1999 09:09:54 +0200 Message-ID: <312.941094594@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , Chuck Rob ey writes: >Lsof is broken. > >I already wrote Poul about it, but he hasn't seen my email yet, I guess. I've been busy, your email is sitting in my inbox somewhere, to be dealt with when I have time. >Does anyone know the direction this was going in, and what visibility the >namecache is intended to have? The namecache is intended to have no visibility from userland. The fact that lsof (with the aid of libkvm) abuses it doesn't change this fact. The lsof functionality should in my opinion be added to the system, and the necessary hooks should be added to the kernel using sysctl. As a short term fix, you can remove the "static", but take this as a first warning: the namecache implementation is NOT an API. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message