SO_LINGER and SO_DONTLINGER

[Jim Jagielski <ji...@jaguNET.com>]

My TCP/IP handbook is miles away... Anyone know offhand waht SO_DONTLINGER
does to process the request "as quickly as possible"?

The reason: I have 2 A/UX boxes which I'm testing lingering_close on.
  Every 10 mins I have a cron job check the number of WAIT_2 stats
  and log that. It's looking like lingering_close causes more of
  these than without (~20 on one server and ~40 on another, each
  ave about 50khits/day or so). I'm thinking about seeing what
  SO_LINGER does (I seem to recall that it was buggy on SysV4
  platforms mostly) to help, but am also curious what SO_DONTLINGER
  might do.


-- 
====================================================================
      Jim Jagielski            |       jaguNET Access Services
     jim@jaguNET.com           |       http://www.jaguNET.com/
                  "Not the Craw... the CRAW!"

Re: SO_LINGER and SO_DONTLINGER

[Chuck Murcko <ch...@topsail.org>]

Jim Jagielski wrote:
> 
> My TCP/IP handbook is miles away... Anyone know offhand waht SO_DONTLINGER
> does to process the request "as quickly as possible"?
> 
> The reason: I have 2 A/UX boxes which I'm testing lingering_close on.
>   Every 10 mins I have a cron job check the number of WAIT_2 stats
>   and log that. It's looking like lingering_close causes more of
>   these than without (~20 on one server and ~40 on another, each
>   ave about 50khits/day or so). I'm thinking about seeing what
>   SO_LINGER does (I seem to recall that it was buggy on SysV4
>   platforms mostly) to help, but am also curious what SO_DONTLINGER
>   might do.
> 
If SO_LINGER is set, and the linger time is zero, any data remaining to
be sent is discarded when the socket is closed. If the linger time is
nonzero (positive 8^) the system attempts to deliver unsent data for the
time in seconds specified.
-- 
chuck
Chuck Murcko
The Topsail Group, West Chester PA USA
chuck@topsail.org