<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	
	>
<channel>
	<title>
	Comments on: How to Stop a Process Blocking a Port in Linux	</title>
	<atom:link href="https://www.tecmint.com/kill-process-using-port-linux/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.tecmint.com/kill-process-using-port-linux/</link>
	<description>Tecmint - Linux Howtos, Tutorials, Guides, News, Tips and Tricks.</description>
	<lastBuildDate>Fri, 22 May 2026 03:28:09 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	
	<item>
		<title>
		By: Ravi Saive		</title>
		<link>https://www.tecmint.com/kill-process-using-port-linux/comment-page-1/#comment-2413407</link>

		<dc:creator><![CDATA[Ravi Saive]]></dc:creator>
		<pubDate>Fri, 22 May 2026 03:28:09 +0000</pubDate>
		<guid isPermaLink="false">https://www.tecmint.com/?p=61944#comment-2413407</guid>

					<description><![CDATA[In reply to &lt;a href=&quot;https://www.tecmint.com/kill-process-using-port-linux/comment-page-1/#comment-2413192&quot;&gt;Pranshu Parmar&lt;/a&gt;.

@Pranshu,

Nice, &lt;code&gt;witr&lt;/code&gt; looks like a clean way to wrap the usual &lt;code&gt;lsof&lt;/code&gt;, &lt;code&gt;netstat&lt;/code&gt;, &lt;code&gt;ps&lt;/code&gt;, &lt;code&gt;kill&lt;/code&gt; steps.

The interactive view is the best part since you can quickly see what’s using a port and act on it without switching commands all the time.

Much faster and simpler than juggling multiple tools. I’ll write a post on this.]]></description>
			<content:encoded><![CDATA[<p>In reply to <a target="_blank" href="https://www.tecmint.com/kill-process-using-port-linux/comment-page-1/#comment-2413192">Pranshu Parmar</a>.</p>
<p>@Pranshu,</p>
<p>Nice, <code>witr</code> looks like a clean way to wrap the usual <code>lsof</code>, <code>netstat</code>, <code>ps</code>, <code>kill</code> steps.</p>
<p>The interactive view is the best part since you can quickly see what’s using a port and act on it without switching commands all the time.</p>
<p>Much faster and simpler than juggling multiple tools. I’ll write a post on this.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Pranshu Parmar		</title>
		<link>https://www.tecmint.com/kill-process-using-port-linux/comment-page-1/#comment-2413192</link>

		<dc:creator><![CDATA[Pranshu Parmar]]></dc:creator>
		<pubDate>Thu, 21 May 2026 09:23:10 +0000</pubDate>
		<guid isPermaLink="false">https://www.tecmint.com/?p=61944#comment-2413192</guid>

					<description><![CDATA[Another handy option for this use case is witr - https://github.com/pranshuparmar/witr

Instead of chaining multiple commands to find and inspect processes attached to a port, it gives you interactive view where you can directly see the process(es) using a specific port, inspect details in human readable format, and even take actions on them interactively.

Makes port/process inspection much faster compared to jumping between &lt;code&gt;lsof&lt;/code&gt;, &lt;code&gt;netstat&lt;/code&gt;, &lt;code&gt;ps&lt;/code&gt;, and &lt;code&gt;kill&lt;/code&gt;.]]></description>
			<content:encoded><![CDATA[<p>Another handy option for this use case is witr &#8211; <a target="_blank" href="https://github.com/pranshuparmar/witr" rel="nofollow ugc">https://github.com/pranshuparmar/witr</a></p>
<p>Instead of chaining multiple commands to find and inspect processes attached to a port, it gives you interactive view where you can directly see the process(es) using a specific port, inspect details in human readable format, and even take actions on them interactively.</p>
<p>Makes port/process inspection much faster compared to jumping between <code>lsof</code>, <code>netstat</code>, <code>ps</code>, and <code>kill</code>.</p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
