<?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>Smartkey - Java Software Consultancy &#187; Other</title>
	<atom:link href="http://blog.smartkey.co.uk/category/other/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.smartkey.co.uk</link>
	<description></description>
	<lastBuildDate>Fri, 06 Apr 2012 16:06:02 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Identifying which processes are using network ports on a Mac</title>
		<link>http://blog.smartkey.co.uk/2012/02/identifying-which-processes-are-using-network-ports-on-a-mac/</link>
		<comments>http://blog.smartkey.co.uk/2012/02/identifying-which-processes-are-using-network-ports-on-a-mac/#comments</comments>
		<pubDate>Thu, 09 Feb 2012 11:16:54 +0000</pubDate>
		<dc:creator>Steve Neal</dc:creator>
				<category><![CDATA[Linux]]></category>
		<category><![CDATA[linux]]></category>
		<category><![CDATA[Mac]]></category>
		<category><![CDATA[Networking]]></category>
		<category><![CDATA[OS X]]></category>

		<guid isPermaLink="false">http://blog.smartkey.co.uk/?p=968</guid>
		<description><![CDATA[Typically I&#8217;d use netstat&#8217;s -o flag to identify the process ID when listing networking activity from a Linux/Unix machine. Unfortunately this option is not available with netstat on  Mac OS X.
I recently has a rogue process (I suspected a virus) on my Mac that was creating thousands of connections out to hosting providers. Luckily I [...]]]></description>
			<content:encoded><![CDATA[<p>Typically I&#8217;d use netstat&#8217;s -o flag to identify the process ID when listing networking activity from a Linux/Unix machine. Unfortunately this option is not available with netstat on  Mac OS X.</p>
<p>I recently has a rogue process (I suspected a virus) on my Mac that was creating thousands of connections out to hosting providers. Luckily I found this fix, which uses lsof to list the network files that are being held open instead. It works a treat:</p>
<pre>~$ lsof -i -P</pre>
<p>The -i flag restricts output to the networking files, the -P flag prevents well known port numbers from being converted from numbers to text (e.g. 80 -&gt; http). Try it without the -P flag to see the protocol short names.</p>
<p>Using this command, I identified which process was creating the unwanted connections and to dealt with it.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.smartkey.co.uk/2012/02/identifying-which-processes-are-using-network-ports-on-a-mac/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Count the processors on a Linux server</title>
		<link>http://blog.smartkey.co.uk/2011/06/count-the-processors-on-a-linux-server/</link>
		<comments>http://blog.smartkey.co.uk/2011/06/count-the-processors-on-a-linux-server/#comments</comments>
		<pubDate>Thu, 02 Jun 2011 14:46:16 +0000</pubDate>
		<dc:creator>Steve Neal</dc:creator>
				<category><![CDATA[Linux]]></category>
		<category><![CDATA[Command]]></category>
		<category><![CDATA[linux]]></category>
		<category><![CDATA[Unix]]></category>

		<guid isPermaLink="false">http://blog.smartkey.co.uk/?p=918</guid>
		<description><![CDATA[If you need to see how many processors there are available on a Linu/Unix server, use the following command from your shell:
cat /proc/cpuinfo &#124; grep processor
each of the processors will be listed in the output. For example, on a server I use the output looks like this:

processor       : 0
processor [...]]]></description>
			<content:encoded><![CDATA[<p>If you need to see how many processors there are available on a Linu/Unix server, use the following command from your shell:</p>
<p><code>cat /proc/cpuinfo | grep processor</code></p>
<p>each of the processors will be listed in the output. For example, on a server I use the output looks like this:</p>
<p><code><br />
processor       : 0<br />
processor       : 1<br />
processor       : 2<br />
processor       : 3<br />
processor       : 4<br />
processor       : 5<br />
processor       : 6<br />
processor       : 7<br />
</code></p>
<p>So, on this server we can see there are 8 processors available.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.smartkey.co.uk/2011/06/count-the-processors-on-a-linux-server/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Deleting all files over a certain age on a Linux server</title>
		<link>http://blog.smartkey.co.uk/2011/05/deleting-files-over-a-certain-age-on-a-linux-server/</link>
		<comments>http://blog.smartkey.co.uk/2011/05/deleting-files-over-a-certain-age-on-a-linux-server/#comments</comments>
		<pubDate>Wed, 04 May 2011 15:38:58 +0000</pubDate>
		<dc:creator>Steve Neal</dc:creator>
				<category><![CDATA[Linux]]></category>
		<category><![CDATA[Other]]></category>
		<category><![CDATA[linux]]></category>

		<guid isPermaLink="false">http://blog.smartkey.co.uk/?p=913</guid>
		<description><![CDATA[To delete files on a Linux server that are all over 3 days old, use this:

find /log/ -type f -mtime -3 -exec rm {} \;

This command will find all files in /log over 3 days old and will run the rm command for each of them.
]]></description>
			<content:encoded><![CDATA[<p>To delete files on a Linux server that are all over 3 days old, use this:<br />
<code><br />
find /log/ -type f -mtime -3 -exec rm {} \;<br />
</code><br />
This command will find all files in /log over 3 days old and will run the rm command for each of them.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.smartkey.co.uk/2011/05/deleting-files-over-a-certain-age-on-a-linux-server/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
	</channel>
</rss>

