{"version":"2.1.319","anchor":"socket-owner-lookup-reads-proc-in-bounded-batches","canonical_anchor":"socket-owner-lookup-reads-proc-in-bounded-batches","heading":"Finding which program owns a connection is lighter on busy Linux machines","tier":"notice","area":"Elsewhere","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319\/e\/socket-owner-lookup-reads-proc-in-bounded-batches","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319","markdown":"### Finding which program owns a connection is lighter on busy Linux machines\n\nOn Linux, Claude Code now looks up the owner of a connection a batch of programs at a time, newest first, instead of all at once\n\n**What**\n\nOn Linux, Claude Code sometimes needs to find which running program owns a socket (an open network or local connection). It does this by reading `\/proc`, a special folder where Linux describes every running program. It used to read the details of every program at once. It now:\n\n- Checks the newest programs first\n\n- Reads them in batches that grow as it goes\n\n- Remembers recent matches and tries those first\n\n**Why**\n\nThe lookup costs less on machines running many programs.\n\n- Area: Elsewhere\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 0\/5\n- Scope: individual\n- Heads-up: no"}