On Fri, Feb 15, 2002 at 07:35:39PM -0800, Terry Lambert wrote:
> > > Maybe it's losing an open instance in the resource
> > > track on close? That seems the most likely culprit...
> > Do you mean in the linux emu case?
> > If so, please see my message stating that I also used a linux emu program
> > to test this.
> > If not, can you please be a bit more detailed?
> I saw your message. It wasn't clear to me that you were
> simply exiting in the test, instead of actually closing
> the descriptor. I suspect that vmware just exits, and
> expects a resource tracking close on exit to free the
> reference count. If the Linux ABI code has not been
> updated with all the necessary hand waving (old code was
> OK, new code is broke ::= that's what's happening), then
> that could easily cause the problem, whereas a test case
> that does all the right manual shutdown would not have a
I did do an explicit close() in my test.
However, using ktrace I also see a explicit close from vmware.
That one doesn't reach the tap device however.
So we are back to the original question, where does the close gets lost.
Mark Santcroos RIPE Network Coordination Centre
http://www.ripe.net/home/mark/ New Projects Group/TTM
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message