<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: last_ack in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/last-ack/m-p/3901497#M84534</link>
    <description>This script may be helpfull for you - &lt;A href="http://www.demailly.com/~dl/force_close_tcp" target="_blank"&gt;http://www.demailly.com/~dl/force_close_tcp&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;regards,&lt;BR /&gt;ivan</description>
    <pubDate>Mon, 20 Nov 2006 17:07:10 GMT</pubDate>
    <dc:creator>Ivan Krastev</dc:creator>
    <dc:date>2006-11-20T17:07:10Z</dc:date>
    <item>
      <title>last_ack</title>
      <link>https://community.hpe.com/t5/operating-system-linux/last-ack/m-p/3901496#M84533</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;How can I get around a port that is in LAST_ACK state.  I'm currently running hpux 11.23 on an itanium machine.  My tcp_fin_wait_2_timeout value is set at 30000 in the nddconf file.  Sometime when we stop our listener the process could not restart because of this issue.&lt;BR /&gt;&lt;BR /&gt;Thanks,</description>
      <pubDate>Mon, 20 Nov 2006 16:52:29 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/last-ack/m-p/3901496#M84533</guid>
      <dc:creator>christian_derek</dc:creator>
      <dc:date>2006-11-20T16:52:29Z</dc:date>
    </item>
    <item>
      <title>Re: last_ack</title>
      <link>https://community.hpe.com/t5/operating-system-linux/last-ack/m-p/3901497#M84534</link>
      <description>This script may be helpfull for you - &lt;A href="http://www.demailly.com/~dl/force_close_tcp" target="_blank"&gt;http://www.demailly.com/~dl/force_close_tcp&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;regards,&lt;BR /&gt;ivan</description>
      <pubDate>Mon, 20 Nov 2006 17:07:10 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/last-ack/m-p/3901497#M84534</guid>
      <dc:creator>Ivan Krastev</dc:creator>
      <dc:date>2006-11-20T17:07:10Z</dc:date>
    </item>
    <item>
      <title>Re: last_ack</title>
      <link>https://community.hpe.com/t5/operating-system-linux/last-ack/m-p/3901498#M84535</link>
      <description>UX isn't Linux but still...&lt;BR /&gt;&lt;BR /&gt;If you are unable to restart a server application because there are previous connections it suggests the server code is broken and needs to be fixed by adding a setsockopt() to set SO_REUSEADDR.  That will allow the server to re-establish its LISTEN endpoint while there are still old connections waiting to clean-up.&lt;BR /&gt;&lt;BR /&gt;Killing a connection via ndd/scripts is a _last resort_ , and the tcp_fin_wait_2 timer is a kludge.</description>
      <pubDate>Tue, 21 Nov 2006 12:40:52 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/last-ack/m-p/3901498#M84535</guid>
      <dc:creator>rick jones</dc:creator>
      <dc:date>2006-11-21T12:40:52Z</dc:date>
    </item>
  </channel>
</rss>

