<?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>Ramblings from MostlyChris &#187; Linux</title>
	<atom:link href="http://blog.mostlychris.com/tag/linux/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.mostlychris.com</link>
	<description>Tech stuff and a bit more</description>
	<lastBuildDate>Tue, 27 Dec 2011 14:23:25 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>tcpdump for Wireshark</title>
		<link>http://blog.mostlychris.com/2009/06/tcpdump-for-wireshark/</link>
		<comments>http://blog.mostlychris.com/2009/06/tcpdump-for-wireshark/#comments</comments>
		<pubDate>Sat, 20 Jun 2009 14:27:24 +0000</pubDate>
		<dc:creator>Chris</dc:creator>
				<category><![CDATA[Linux]]></category>
		<category><![CDATA[SOAP]]></category>
		<category><![CDATA[tcpdump]]></category>
		<category><![CDATA[Wireshark]]></category>

		<guid isPermaLink="false">http://blog.mostlychris.com/?p=494</guid>
		<description><![CDATA[I have this problem. I am trying to send a SOAP request to a provider of information I need. In order to make this request correctly, I have to provide a value as a LONG. For whatever reason, they are not getting what I think I am sending. Therefore, I need a way to see [...]]]></description>
		<wfw:commentRss>http://blog.mostlychris.com/2009/06/tcpdump-for-wireshark/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Simple Sorts</title>
		<link>http://blog.mostlychris.com/2009/04/simple-sorts/</link>
		<comments>http://blog.mostlychris.com/2009/04/simple-sorts/#comments</comments>
		<pubDate>Sat, 18 Apr 2009 07:46:28 +0000</pubDate>
		<dc:creator>Chris</dc:creator>
				<category><![CDATA[Commands]]></category>
		<category><![CDATA[awk]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[log parsing]]></category>
		<category><![CDATA[sort]]></category>
		<category><![CDATA[uniq]]></category>

		<guid isPermaLink="false">http://blog.mostlychris.com/?p=381</guid>
		<description><![CDATA[Since I am apparently unable to remember how to do a simple sort, I'm going to throw it into my blog so I can refer to it later. In this particular case, I was attempting to pull out all of the "from=" entries in the server's mail logs. I won't go into the details of [...]]]></description>
		<wfw:commentRss>http://blog.mostlychris.com/2009/04/simple-sorts/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Urchin Stats: Unable to open database for writing since it has been archived</title>
		<link>http://blog.mostlychris.com/2009/04/urchin-stats-unable-to-open-database-for-writing-since-it-has-been-archived/</link>
		<comments>http://blog.mostlychris.com/2009/04/urchin-stats-unable-to-open-database-for-writing-since-it-has-been-archived/#comments</comments>
		<pubDate>Sat, 18 Apr 2009 05:49:18 +0000</pubDate>
		<dc:creator>Chris</dc:creator>
				<category><![CDATA[General]]></category>
		<category><![CDATA[errors]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[urchin]]></category>

		<guid isPermaLink="false">http://blog.mostlychris.com/?p=378</guid>
		<description><![CDATA[If you encounter the following error when running the Urchin stats update it can easily be corrected. "Unable to open database for writing since it has been archived" The error occurs whenever Urchin has archived its log tracking databases. The fix for this is pretty simple. 1. Navigate to /usr/local/urchin/data/reports/[profile] 2. Unznip the [date]-archive.zip files [...]]]></description>
		<wfw:commentRss>http://blog.mostlychris.com/2009/04/urchin-stats-unable-to-open-database-for-writing-since-it-has-been-archived/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>File Access Control List</title>
		<link>http://blog.mostlychris.com/2009/04/file-access-control-list/</link>
		<comments>http://blog.mostlychris.com/2009/04/file-access-control-list/#comments</comments>
		<pubDate>Sat, 04 Apr 2009 08:18:56 +0000</pubDate>
		<dc:creator>Chris</dc:creator>
				<category><![CDATA[Disk]]></category>
		<category><![CDATA[facl]]></category>
		<category><![CDATA[files]]></category>
		<category><![CDATA[Linux]]></category>

		<guid isPermaLink="false">http://blog.mostlychris.com/?p=372</guid>
		<description><![CDATA[Lets suppose you have a shared httpdocs directory on your server in which you would like to have your developers gain access. However, there is going to be more than one developer and each one will have their own login credentials. This becomes a problem because of file ownership permissions. If one developer has uploaded [...]]]></description>
		<wfw:commentRss>http://blog.mostlychris.com/2009/04/file-access-control-list/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Fixing Journal Abort Filesystem Problems</title>
		<link>http://blog.mostlychris.com/2009/04/fixing-journal-abort-filesystem-problems/</link>
		<comments>http://blog.mostlychris.com/2009/04/fixing-journal-abort-filesystem-problems/#comments</comments>
		<pubDate>Sat, 04 Apr 2009 05:08:13 +0000</pubDate>
		<dc:creator>Chris</dc:creator>
				<category><![CDATA[Linux]]></category>
		<category><![CDATA[filesystem]]></category>
		<category><![CDATA[journal]]></category>

		<guid isPermaLink="false">http://blog.mostlychris.com/?p=365</guid>
		<description><![CDATA[I routinely deal with Read Only file systems and always have to remember the commands to remove the journal and run a file system check. Since some days I am better at remembering than others, I thought I'd just write it down in this post so I can find it later. First, remove the journal: [...]]]></description>
		<wfw:commentRss>http://blog.mostlychris.com/2009/04/fixing-journal-abort-filesystem-problems/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

