<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>fedora &#8211; it.megocollector.com</title>
	<atom:link href="https://it.megocollector.com/tag/fedora/feed/" rel="self" type="application/rss+xml" />
	<link>https://it.megocollector.com</link>
	<description>The information technology compendium</description>
	<lastBuildDate>Sat, 30 May 2026 23:39:23 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=7.0.3</generator>
	<item>
		<title>Use netstat in Linux to determine port conflicts</title>
		<link>https://it.megocollector.com/tips-and-tricks/use-netstat-in-linux-to-determine-port-conflicts/</link>
		
		<dc:creator><![CDATA[admin]]></dc:creator>
		<pubDate>Fri, 07 Nov 2008 10:38:00 +0000</pubDate>
				<category><![CDATA[Linux]]></category>
		<category><![CDATA[Tips and Tricks]]></category>
		<category><![CDATA[centos 5]]></category>
		<category><![CDATA[fedora]]></category>
		<category><![CDATA[netstat]]></category>
		<category><![CDATA[port conflict]]></category>
		<category><![CDATA[red hat enterprise linux 5]]></category>
		<category><![CDATA[rhel 5]]></category>
		<guid isPermaLink="false">https://it.megocollector.com/?p=880</guid>

					<description><![CDATA[After installing an application that required port 8080, the application failed to start because the port was already in use. Changing the new application to use port 8090 worked, but it still left the question of what was running on 8080. As on Windows, Linux provides a command‑line utility, netstat, which can be used to inspect open ports and the...]]></description>
		
		
		
			</item>
		<item>
		<title>Accessing JBoss on RHEL/CentOS — Firewall Gotcha (and the Right Way to Handle It)</title>
		<link>https://it.megocollector.com/scripts/disable-firewall-on-red-hat-enterprise-linux-rhel/</link>
		
		<dc:creator><![CDATA[admin]]></dc:creator>
		<pubDate>Tue, 23 Sep 2008 17:03:51 +0000</pubDate>
				<category><![CDATA[Linux]]></category>
		<category><![CDATA[Scripts]]></category>
		<category><![CDATA[Tips and Tricks]]></category>
		<category><![CDATA[CentOS]]></category>
		<category><![CDATA[chkconfig]]></category>
		<category><![CDATA[disable firewall]]></category>
		<category><![CDATA[fedora]]></category>
		<category><![CDATA[iptables]]></category>
		<category><![CDATA[red hat]]></category>
		<category><![CDATA[rhel]]></category>
		<guid isPermaLink="false">https://it.megocollector.com/?p=663</guid>

					<description><![CDATA[While setting up JBoss (with its bundled Tomcat) on a freshly installed Red Hat–based system, everything appeared to be running correctly. The service started cleanly, and the default web interface was bound to port 8080 as expected. However, when attempting to access the application from a remote machine, the connection failed. After a bit of troubleshooting, the issue turned out...]]></description>
		
		
		
			</item>
	</channel>
</rss>
