Casper Dik wrote:

Is this not just a case of things changing underneat ipfstat?


Kmem readers do not lock out concurrent activity so they can try to follow
stale pointers.

Since I didn't get a response to this, I'll try one more time...


So, yeah, it does seem this only happens when ipf has stuff change under it

BUT, doesn't that imply that when IPF detaches from interfaces its not cleaning up properly? Or am I just not understanding the properly?


-- Phil Dibowitz [EMAIL PROTECTED] Freeware and Technical Pages Insanity Palace of Metallica http://home.earthlink.net/~jaymzh666/ http://www.ipom.com/

"They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety."
 - Benjamin Franklin, 1759




Reply via email to