From 3e4c5a6261770bced301b5e74233e7866166ea5b Mon Sep 17 00:00:00 2001 From: Christian Krinitsin Date: Sun, 1 Jun 2025 21:35:14 +0200 Subject: clean up repository --- .../target_missing/host_missing/accel_missing/1949 | 12 ------------ 1 file changed, 12 deletions(-) delete mode 100644 gitlab/issues_text/target_missing/host_missing/accel_missing/1949 (limited to 'gitlab/issues_text/target_missing/host_missing/accel_missing/1949') diff --git a/gitlab/issues_text/target_missing/host_missing/accel_missing/1949 b/gitlab/issues_text/target_missing/host_missing/accel_missing/1949 deleted file mode 100644 index d7a5e7db3..000000000 --- a/gitlab/issues_text/target_missing/host_missing/accel_missing/1949 +++ /dev/null @@ -1,12 +0,0 @@ -chardev zombie TCP session -Description of problem: -When user terminates TCP session ungracefully (eg: power-cycle or network cable disconnect), the TCP session keeps in established status forever. In this state, new sessions can't access the chardev, since the zombie TCP session keeps exclusive access to chardev. -Steps to reproduce: -1.Establish client session to chardev TCP socket. -2.Power-off the client machine. -3.Establish a new client session -4.Observe that old TCP session is never killed and new session can connect but not interact with chardev. -Additional information: -Suggestions to resolve this and improve the chardev feature: -- enable TCP keep-alive for chardev server. -- allow multiple client sessions concurrently, where chardev output is broadcasted to all client sessions, and chardev input is shared by all clients. -- cgit 1.4.1