🚀 go-pugleaf

In article <memo.36812@cix.compulink.co.uk> Gareth Howell <garethh@cix.compulink.co.uk> writes:

   Has anybody modified NOS to support this option on its sockets? It
   sure would be useful sometimes.

No, it would NOT be useful.  Keep-alives are the work of the devil.
However, machines *do* crash, networks *do* go down, etc.  So what to
do?  The solution is to apply an upper bound to the amount of
resources that can be consumed by your networking software.  Whenever
the system runs out of resources, it recovers resources from the least
recently used (LRU) connection.

A network package either needs keep-alives (gag), or resource recovery.
Phil is, to my mind, remiss in not including resource recovery in NOS,
given his dislike of keep-alives.

   Let's face it, in an amateur environment, end nodes do dissappear
   temporarily occasionally; the ability to detect this, reset the
   session, and restart the mail transfer at the next smtp timer
   tick would increase overall system availability.

If it's only temporary, why give up on it?

--russ <nelson@clutx.clarkson.edu> I'm proud to be a humble Quaker.
Clear cutting is criminal, spiking trees is criminal, and using hyperbole of
this magnitude in a serious discussion is criminal.  -- Irv Chidsey
-- 
*****************************************************************
   ___  ____  ___    _  _ ___ ___   ___ ___ ___     ___ _  _
  /__/ / / /   /    /\ / /__   /   /__//__//   /__//__ /\ /
 / \  /   / __/_   /  / /__   /   /  //  //__ /  //__ /  /