On Sat, 2002-08-31 at 03:01, Peter Palmreuther wrote: > > JA> Netstat might not show an internal component having an open connection > JA> if Windows has terminated the connection, and the component didn't > JA> acknowledge it. > > So the socket _ain't_ open. > the TCP stack does not know anything about it, therefore the socket ain't > open, it's only the component that hangs ... my words ...
It was actually Marck that suggested it may be an internal component that is not recording the disconnect. I cannot however see a method of recreating that issue without maybe the source so I can terminate the connection from inside the environment, and trace through what is going on. I'd still be curious to see if they are using a global boolean to record a connection though. > JA> This wasn't the kind of connection termination I was thinking of. The > JA> daemon in this case drops the connections safely, and reports valid > JA> terminations... > > No. I killed it '-9' with no chance to do _anything_. I plugged out the > cable, so no chance to report and acknowledge _anything_ .... Hrm... then Windows is sending a valid connection terminate to the client, and it is acknowledging it safely, and terminating the connection. So it is clearly not that. There must be some other factor. -- Jonathan Angliss ([EMAIL PROTECTED]) ________________________________________________ Current version is 1.61 | "Using TBUDL" information: http://www.silverstones.com/thebat/TBUDLInfo.html
