1973a417   
   From: grahn+nntp@snipabacken.se   
      
   On Thu, 25 Jun 2009 06:42:23 -0700 (PDT), Marco Peng    
   wrote:   
      
   [top-posting fixed]   
      
   > On Jun 24, 5:28 pm, Marco Peng  wrote:   
   >> Hi All   
   >>   
   >> 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!   
      
   > thanks everyone. I noticed the TCP timeout mechanism, but specially,   
   > I use  tcpsvd to limit the concurrent dropbear handled connection.   
   > It's I mentioned early "tcpsvd -vv -c 1 -C 1 0 22 /usr/sbin/dropbear -   
   > r /etc/rsa_key.priv -i -   
   > E -x &"   
   > So is there any other concern on this service form?   
   > in this mode, dropbear will not create a real socket, how can I   
   setsockopt()??   
      
   Are you sure its fd 0/1 isn't a real socket?   
      
   > I can only change the dropbear code. is there a way to achieve my   
   > goal?   
      
   First do what Barry Magol suggested and explain why you need to do   
   this. You are asking for trouble when you forbid more than one   
   connection, and make sure clients get hung a lot.   
      
   /Jorgen   
      
   --   
     // Jorgen Grahn           R'lyeh wgah'nagl fhtagn!   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)