but after a while, there is no Response
Do you mean there is no response from the task or from the user of the command line interpreter?
I suppose that you found ‘
‘ already, along with the warnings about freeing the memories and other resources?
In stead of creating a task per user (or per session), you might also consider creating a single task that serves all users. Every new user that comes in gets a memory object (which stores its status, command history, etc). That object may also contain an idle timer, so that the session will be closed and resources freed after a period of inactivity.