>I am trying to understand the problem here.It boils down to: >If a client quits (is forced to quit) by what ever means >during a file transfer the node will hang hard. > > Right? > And it has to be a connection via TCP/IP ?
No, its just that TCP IP (on the Mac) takes a LONG time to notice that the conenction is bye-bye. So the user will appear logged in until TCP reports the connection loss. Usually, TF will hit the idle timeout first, but since the connection is really dead,but TCP doesn'tknow...
Well finally the whole thing times out and the node comes free. But its not locked up, its just as if a user is still logged in, but idle.
