e879e849   
   From: rick.jones2@hp.com   
      
   Marco Peng  wrote:   
      
   > Thanks for your reading. :-)   
   > I meet a problem, I use dropbear as a ssh server.   
   > I limit the concurrent session max = 1.   
   > If I login after a logout, all work good.   
   > But if I shutdown my client without logout, I cannot login again.   
   > Can some one give my some hints to handle this case ?   
   > How can I change the system TCP session time out for my next login   
   > without the last logout?   
      
   > The server OS is linux 2.6   
   > I limit the concurrent session max =1 with the instruction:   
   > "tcpsvd -vv -c 1 -C 1 0 22 /usr/sbin/dropbear -r /etc/rsa_key.priv -i -   
   > E -x &"   
      
   > any response will be appreciated!   
      
   If I recall correctly, ssh defines an application-layer keepalive   
   mechanism.  It would be best to look into enabling that to clear-out   
   your half-open sessions.   
      
   rick jones   
   --   
   I don't interest myself in "why." I think more often in terms of   
   "when," sometimes "where;" always "how much."  - Joubert   
   these opinions are mine, all mine; HP might not want them anyway... :)   
   feel free to post, OR email to rick.jones2 in hp.com but NOT BOTH...   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)