8 messages in org.freebsd.freebsd-currentRe: lsof + namecache | From | Sent On | Attachments |
|---|---|---|
| Chuck Robey | Oct 27, 1999 7:03 am | |
| Poul-Henning Kamp | Oct 28, 1999 12:09 am | |
| Garrett Wollman | Oct 28, 1999 7:52 am | |
| Greg Lehey | Oct 28, 1999 8:06 am | |
| David O'Brien | Oct 28, 1999 8:53 am | |
| Garrett Wollman | Oct 28, 1999 8:54 am | |
| Dan Nelson | Oct 28, 1999 10:35 am | |
| David O'Brien | Oct 28, 1999 10:39 am |
| Subject: | Re: lsof + namecache | |
|---|---|---|
| From: | Poul-Henning Kamp (ph...@critter.freebsd.dk) | |
| Date: | Oct 28, 1999 12:09:32 am | |
| List: | org.freebsd.freebsd-current | |
In message <Pine...@picnic.mat.net>, 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 ph...@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 majo...@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message