look like the _process_message_thread won't stop. about smbprotocol HOT 2 CLOSED

Thanks for bringing this up, a thread should definitely be linked to the connection and stopped once the connection is disconnected.

from smbprotocol.

Sorry for the delay but I had another look into this and the threads for each connection will be stopped when you run .disconnect(). In the diconnect() function it calls self.transport.close()

Part of closing the transport is to close the socket by sending the shutdown signal, waiting for that thread to finish then finally closing the socket

When the actual socket is shutdown by either the client or the server, it is set to always add None to the connection thread queue

Finally once the recv_queue receives None (the socket has been closed) it exits the process which subsequently stops the thread

If you are finding this is not the case on your setup I'm happy to have a further look but it does seem like the thread will be cleaned up when you disconnect from the connection. Even when running a test I found that the only thread still running after calling .disconnect() is the main thread.

from smbprotocol.