<?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>Nomad Labs Code</title>
	<atom:link href="http://code.nomad-labs.com/feed/" rel="self" type="application/rss+xml" />
	<link>http://code.nomad-labs.com</link>
	<description>srasul&#039;s snippets of code and thought</description>
	<lastBuildDate>Wed, 15 May 2013 09:37:09 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.1</generator>
		<item>
		<title>Some tips on java.lang.OutOfMemoryError: unable to create new native thread</title>
		<link>http://code.nomad-labs.com/2012/12/20/some-tips-on-java-lang-outofmemoryerror-unable-to-create-new-native-thread/</link>
		<comments>http://code.nomad-labs.com/2012/12/20/some-tips-on-java-lang-outofmemoryerror-unable-to-create-new-native-thread/#comments</comments>
		<pubDate>Thu, 20 Dec 2012 18:03:32 +0000</pubDate>
		<dc:creator>srasul</dc:creator>
				<category><![CDATA[Java]]></category>
		<category><![CDATA[linux]]></category>

		<guid isPermaLink="false">http://code.nomad-labs.com/?p=238</guid>
		<description><![CDATA[Thats right, the dreaded, java.lang.OutOfMemoryError: unable to create new native thread. I fixed one of these the other day. And I will present to you how I did it. The cause for such errors are usually Thread Leaks. A Thread Leak is where some ass hat is creating threads which never die. Another reason for [...]]]></description>
		<wfw:commentRss>http://code.nomad-labs.com/2012/12/20/some-tips-on-java-lang-outofmemoryerror-unable-to-create-new-native-thread/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Debugging vs Writing shit</title>
		<link>http://code.nomad-labs.com/2012/07/13/debugging-vs-writing-shit/</link>
		<comments>http://code.nomad-labs.com/2012/07/13/debugging-vs-writing-shit/#comments</comments>
		<pubDate>Fri, 13 Jul 2012 16:59:11 +0000</pubDate>
		<dc:creator>srasul</dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://code.nomad-labs.com/?p=223</guid>
		<description><![CDATA[Great quote I saw today: "Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it." -- Brian W. Kernighan Ma homie Kernighan! Nigga wrote the book on C. Incidentally not many people [...]]]></description>
		<wfw:commentRss>http://code.nomad-labs.com/2012/07/13/debugging-vs-writing-shit/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Mother F**k the ScheduledExecutorService!</title>
		<link>http://code.nomad-labs.com/2011/12/09/mother-fk-the-scheduledexecutorservice/</link>
		<comments>http://code.nomad-labs.com/2011/12/09/mother-fk-the-scheduledexecutorservice/#comments</comments>
		<pubDate>Fri, 09 Dec 2011 15:12:51 +0000</pubDate>
		<dc:creator>srasul</dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://code.nomad-labs.com/?p=212</guid>
		<description><![CDATA[Thats right! Motherfuck this service. Deep hidden in the javadoc of this magnificent class is this gem &#8220;If any execution of the task encounters an exception, subsequent executions are suppressed.&#8221;. In other words, if your runnable task has any fuckups, your task will no longer be run. What sucks about this, is there is no [...]]]></description>
		<wfw:commentRss>http://code.nomad-labs.com/2011/12/09/mother-fk-the-scheduledexecutorservice/feed/</wfw:commentRss>
		<slash:comments>11</slash:comments>
		</item>
		<item>
		<title>JDK Thread Pool Configuration</title>
		<link>http://code.nomad-labs.com/2011/08/05/jdk-thread-pool-configuration/</link>
		<comments>http://code.nomad-labs.com/2011/08/05/jdk-thread-pool-configuration/#comments</comments>
		<pubDate>Fri, 05 Aug 2011 15:45:14 +0000</pubDate>
		<dc:creator>srasul</dc:creator>
				<category><![CDATA[Java]]></category>

		<guid isPermaLink="false">http://code.nomad-labs.com/?p=205</guid>
		<description><![CDATA[Introduction In any non-trivial application of somewhat significant size you will need Executors to background processing or asynchronous processing, task splitting etc. This is where the JDK executors framework comes in. After recently digging into the JDK Executor framework and digging deeper into Thread Pools, I learned 2 things that i would like to share: [...]]]></description>
		<wfw:commentRss>http://code.nomad-labs.com/2011/08/05/jdk-thread-pool-configuration/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Identifying which Java Thread is consuming most CPU</title>
		<link>http://code.nomad-labs.com/2010/11/18/identifying-which-java-thread-is-consuming-most-cpu/</link>
		<comments>http://code.nomad-labs.com/2010/11/18/identifying-which-java-thread-is-consuming-most-cpu/#comments</comments>
		<pubDate>Thu, 18 Nov 2010 12:31:21 +0000</pubDate>
		<dc:creator>srasul</dc:creator>
				<category><![CDATA[Java]]></category>

		<guid isPermaLink="false">http://code.nomad-labs.com/?p=173</guid>
		<description><![CDATA[I didn&#8217;t come up with this. I was shown how to do this by an esteemed college at work. Introduction Most (if not all) productive systems doing anything important will use more than 1 java thread. And when something goes crazy and your cpu usage is on 100%, it is hard to identify which thread(s) [...]]]></description>
		<wfw:commentRss>http://code.nomad-labs.com/2010/11/18/identifying-which-java-thread-is-consuming-most-cpu/feed/</wfw:commentRss>
		<slash:comments>17</slash:comments>
		</item>
		<item>
		<title>An Improved RMI Tutorial with Eclipse</title>
		<link>http://code.nomad-labs.com/2010/03/26/an-improved-rmi-tutorial-with-eclipse/</link>
		<comments>http://code.nomad-labs.com/2010/03/26/an-improved-rmi-tutorial-with-eclipse/#comments</comments>
		<pubDate>Fri, 26 Mar 2010 18:26:55 +0000</pubDate>
		<dc:creator>srasul</dc:creator>
				<category><![CDATA[eclipse]]></category>
		<category><![CDATA[Java]]></category>
		<category><![CDATA[RMI]]></category>

		<guid isPermaLink="false">http://code.nomad-labs.com/?p=139</guid>
		<description><![CDATA[Introduction There are/have-been heaps of remoting frameworks in java, but RMI being part of the JRE/JDK and therefore having no external dependencies is my personal preference for remoting with java. Its main drawback: the wire protocol is not web-friendly and therefore difficult to go through firewalls (although it is possible). But if used behind the [...]]]></description>
		<wfw:commentRss>http://code.nomad-labs.com/2010/03/26/an-improved-rmi-tutorial-with-eclipse/feed/</wfw:commentRss>
		<slash:comments>34</slash:comments>
		</item>
		<item>
		<title>Simulating dropped packets (aka crappy internets) with iptables</title>
		<link>http://code.nomad-labs.com/2010/03/11/simulating-dropped-packets-aka-crappy-internets-with-iptables/</link>
		<comments>http://code.nomad-labs.com/2010/03/11/simulating-dropped-packets-aka-crappy-internets-with-iptables/#comments</comments>
		<pubDate>Thu, 11 Mar 2010 16:47:16 +0000</pubDate>
		<dc:creator>srasul</dc:creator>
				<category><![CDATA[bash]]></category>
		<category><![CDATA[firewall]]></category>
		<category><![CDATA[iptables]]></category>
		<category><![CDATA[linux]]></category>

		<guid isPermaLink="false">http://code.nomad-labs.com/?p=123</guid>
		<description><![CDATA[Disclaimer #1 I am not an iptables expert. This tip will work best on your local linux development box where you probably have no iptables rules setup. Do not play around with this shit on production machines, unless you know what you are doing. Speak with your friendly sysadmins before doing this on any machine [...]]]></description>
		<wfw:commentRss>http://code.nomad-labs.com/2010/03/11/simulating-dropped-packets-aka-crappy-internets-with-iptables/feed/</wfw:commentRss>
		<slash:comments>6</slash:comments>
		</item>
		<item>
		<title>Auto Install the SUN JDK on Linux</title>
		<link>http://code.nomad-labs.com/2009/10/26/auto-install-the-sun-jdk-on-linux/</link>
		<comments>http://code.nomad-labs.com/2009/10/26/auto-install-the-sun-jdk-on-linux/#comments</comments>
		<pubDate>Mon, 26 Oct 2009 15:09:06 +0000</pubDate>
		<dc:creator>srasul</dc:creator>
				<category><![CDATA[bash]]></category>
		<category><![CDATA[Java]]></category>
		<category><![CDATA[linux]]></category>
		<category><![CDATA[Perl]]></category>

		<guid isPermaLink="false">http://code.nomad-labs.com/?p=109</guid>
		<description><![CDATA[Sometimes (yes it does happen), you need to install the JDK from SUN automatically (without having to answer yes/no to the license). Why? For example in a Kick Start script to auto-install the JDK. And so to do this, here a bash &#038; perl script for this exact purpose. This script works only with the [...]]]></description>
		<wfw:commentRss>http://code.nomad-labs.com/2009/10/26/auto-install-the-sun-jdk-on-linux/feed/</wfw:commentRss>
		<slash:comments>6</slash:comments>
		</item>
		<item>
		<title>Ruby FIX Message Viewer 1.0</title>
		<link>http://code.nomad-labs.com/2009/10/04/ruby-fix-message-viewer-1-0/</link>
		<comments>http://code.nomad-labs.com/2009/10/04/ruby-fix-message-viewer-1-0/#comments</comments>
		<pubDate>Sun, 04 Oct 2009 15:48:28 +0000</pubDate>
		<dc:creator>srasul</dc:creator>
				<category><![CDATA[Financial]]></category>
		<category><![CDATA[FIX]]></category>
		<category><![CDATA[ruby]]></category>

		<guid isPermaLink="false">http://code.nomad-labs.com/?p=106</guid>
		<description><![CDATA[Today I released my Ruby FIX Message Viewer 1.0. This is a command line based FIX message viewer programmed in Ruby. I made it command line because most, if not all, of the FIX logs that I have at work are on a server when I have only ssh access. Rather than copy them over [...]]]></description>
		<wfw:commentRss>http://code.nomad-labs.com/2009/10/04/ruby-fix-message-viewer-1-0/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>scp2here: scp command to here</title>
		<link>http://code.nomad-labs.com/2009/08/14/scp2here-scp-command-to-here/</link>
		<comments>http://code.nomad-labs.com/2009/08/14/scp2here-scp-command-to-here/#comments</comments>
		<pubDate>Fri, 14 Aug 2009 20:10:53 +0000</pubDate>
		<dc:creator>srasul</dc:creator>
				<category><![CDATA[bash]]></category>
		<category><![CDATA[linux]]></category>

		<guid isPermaLink="false">http://code.nomad-labs.com/?p=51</guid>
		<description><![CDATA[I usually need to scp stuff from/over-to servers on a regular basis. And here is a function in .bashrc that I use: #function to get the scp path to here function scp2here { user=`whoami` server=`hostname` pathToHere=`pwd` output=$user"@"$server":"$pathToHere if [ ! -z "$1" ] then output=$output"/"$1 fi echo $output } This function prints out the scp [...]]]></description>
		<wfw:commentRss>http://code.nomad-labs.com/2009/08/14/scp2here-scp-command-to-here/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
