<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>TIME_WAIT on Nalar</title>
    <link>https://nalar.dev/tags/time_wait/</link>
    <description>Recent content in TIME_WAIT on Nalar</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 16 Sep 2026 00:00:00 +0700</lastBuildDate>
    <atom:link href="https://nalar.dev/tags/time_wait/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Linux TCP TIME_WAIT Retains Closed Connection State</title>
      <link>https://nalar.dev/linux-tcp-time-wait-retains-closed-connection-state/</link>
      <pubDate>Wed, 16 Sep 2026 00:00:00 +0700</pubDate>
      <guid>https://nalar.dev/linux-tcp-time-wait-retains-closed-connection-state/</guid>
      <description>&lt;p&gt;A TCP socket can disappear from an application while the kernel still retains state for the closed connection. On Linux, the endpoint that completes the active close commonly enters &lt;code&gt;TIME_WAIT&lt;/code&gt;, keeping enough protocol state to protect a later connection from delayed segments associated with the old one.&lt;/p&gt;&#xA;&lt;p&gt;This state is not evidence that a process forgot to close a file descriptor. The application-visible socket can already be gone. &lt;code&gt;TIME_WAIT&lt;/code&gt; belongs to TCP&amp;rsquo;s connection-lifecycle machinery and persists independently of the process that initiated the close.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
