For begin, a big thanks and a big applause for snap7 project.
I have start Snap7 server (C API) on a Linux system.
I start a client on a another system.
All work fine, server start a new thread to serve the client, client read
values from server.
If I properly close the client, the server close the thread (2015-10-15
14:02:12 [x.x.x.x] Client disconnected by peer).
Now if I start the server and the client, don't close the client and physically
remove the network link (remove the network cord of the client system),
Snap7 server never remove the thread who serve client.
Is there a way to impelement a timeout mechanism who close thread after no
activity period?
For begin, a big thanks and a big applause for snap7 project.
I have start Snap7 server (C API) on a Linux system.
I start a client on a another system.
All work fine, server start a new thread to serve the client, client read
values from server.
If I properly close the client, the server close the thread (2015-10-15
14:02:12 [x.x.x.x] Client disconnected by peer).
Now if I start the server and the client, don't close the client and physically
remove the network link (remove the network cord of the client system),
Snap7 server never remove the thread who serve client.
Is there a way to impelement a timeout mechanism who close thread after no
activity period?
Thanks in advance.
Best regards,
Thomas
I found the answer.
KEEPALIVE is activate in snap7.
I have to wait 2 hours or change settings :
http://www.tldp.org/HOWTO/html_single/TCP-Keepalive-HOWTO/
Thanks you for this beautiful project.
Best regards,
Thomas