From: nospam@mutluit.com   
      
   Jorgen Grahn wrote, On 2011-10-15 18:44:   
   > On Sat, 2011-10-15, um wrote:   
   >> David Goodenough wrote, On 2011-10-13 22:57:   
   >>> I'm working on a server application that absolutely *MUST* be able to   
   >>> restart quickly in the event of a crash or other shutdown.  As in I   
   >>> need to be back up and running within 10 seconds of detecting a   
   >>> crash.  Ubuntu 10.04 LTS if it makes any difference.   
   >>>   
   >>> What's killing me is that the previous server may have left   
   >>> connections in any of FIN_WAIT_[12], LAST_ACK or TIME_WAIT.  Even with   
   >>> SO_REUSEADDR, these "zombie" connections appear to make it so that a   
   >>> new server starting can't successfully bind / listen for incoming   
   >>> connections as soon as it starts up.   
   >>   
   >>   
   >> Hmm. why not do the obvious thing: simply fix the srv-app so that it   
   >> doesn't crash anymore...  :-)   
   >   
   > He didn't say, but I *assume* this fast restart mechanism isn't to be   
   > used as an excuse to provide sub-standard software ...   
      
   He is talking of "crashes or other shutdowns" of the _srv-app_,   
   assuming the OS and HW are still intact. So, then why would one   
   ever shutdown and restart a running server app? The only reason   
   I can think of is maintenance, ie. updating/upgrading the app.   
   For reloading cfg-data etc. one normally doesn't need to restart the app.   
   For a sw-update one usually reserves a time window and announces   
   it in advance...   
   No, it sounds a bad idea what he tries to fix, IMHO the whole   
   concept of the app should be rethought...   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)