What steps will reproduce the problem?
1. Go to the webshell login web page
2. Do NOT login, but close the page/tab
3. Do this 2-3 times
What is the expected output?
The children generated in this way should exit cleanly
What do you see instead?
The children disappear from the process list after a while, but
visiting the webshell login after that gives a Connecting to...
message which hangs indefinitely, until the browser gives up.
What version of the product are you using? On what operating system?
WebShell-0.9.6 on Debian Lenny with Python 2.5.2
Please provide any additional information below.
There is no problem if one logs in and then out. It appears only
when I orphan the process by closing the browser page without
logging in. I can reconnect before the children have exited, but
after that the only way is to kill the root process and restart it.
Since webshell is most needed precisely when there is no other way
to open a terminal, this is a potentially debilitating issue. The
workaround is evidently to carefully kill all orphans manually, but
that is clearly unsatisfactory.
Original issue reported on code.google.com by denissu...@gmail.com on 28 May 2009 at 1:09
Original issue reported on code.google.com by
denissu...@gmail.comon 28 May 2009 at 1:09