dcf4aa36   
   From: barmar@alum.mit.edu   
      
   In article   
   <0df35d0a-48f2-4d6d-90b5-59d9580ba87b@o5g2000prh.googlegroups.com>,   
    David Schwartz  wrote:   
      
   > On Jun 24, 2:28 am, Marco Peng  wrote:   
   >   
   > > I meet a problem, I use dropbear as a ssh server.   
   > > I limit the concurrent session max = 1.   
   >   
   > This strikes me as an incredibly bad idea. If there's some problem   
   > within existing session, you can't log in to fix it, as you have   
   > discovered. Are you really sure that's what you want to do? In any   
   > event, 'dropbear' has a '-K' option to keep the connection active and   
   > a '-I' option to break the connection on inactivity.   
   >   
   > DS   
      
   Everyone's recommending turning on keepalives, but I don't understand   
   why this is necessary for the OP's problem.  It sounds like dropbear has   
   a bug.  When he closes the ssh connection, it should send a FIN and   
   dropbear should realize that the session no longer exists.   
      
   Keepalive is necessary if he pulls the network cable or powers down the   
   client machine without cleanly shutting down ssh first.  But he said   
   "shutdown my client without logout".   
      
   --   
   Barry Margolin, barmar@alum.mit.edu   
   Arlington, MA   
   *** PLEASE don't copy me on replies, I'll read them in the group ***   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)