<?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>Part of the Machine</title>
	<atom:link href="http://partofthemachine.com/feed/" rel="self" type="application/rss+xml" />
	<link>http://partofthemachine.com</link>
	<description></description>
	<lastBuildDate>Thu, 02 Jun 2011 14:04:15 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.2</generator>
		<item>
		<title>Running Transaction Test&#8230; Killed</title>
		<link>http://partofthemachine.com/2011/06/running-transaction-test-killed/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=running-transaction-test-killed</link>
		<comments>http://partofthemachine.com/2011/06/running-transaction-test-killed/#comments</comments>
		<pubDate>Thu, 02 Jun 2011 14:04:15 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://partofthemachine.com/?p=29</guid>
		<description><![CDATA[If you come across &#8216;yum&#8217; suddenly dying during an operation with this message, this is likely the linux OOM killer doing it&#8217;s job. The problem at hand is that the machine you&#8217;re working on has very limited RAM, or SWAP is disabled. When the machine is nearing RAM capacity the OOM killer takes care of [...]]]></description>
			<content:encoded><![CDATA[<p>If you come across &#8216;yum&#8217; suddenly dying during an operation with this message, this is likely the linux OOM killer doing it&#8217;s job. The problem at hand is that the machine you&#8217;re working on has very limited RAM, or SWAP is disabled. When the machine is nearing RAM capacity the OOM killer takes care of taking down the offender.</p>
<p>I first came across this working with a machine in &#8216;rescue&#8217; mode, which has SWAP disabled by default. Enabling it took care of the problem.</p>
<p>If you run &#8216;dmesg&#8217;, you&#8217;ll be able to see something like the following:<br />
Out of memory: Killed process XXXX, UID 0 (yum).</p>
]]></content:encoded>
			<wfw:commentRss>http://partofthemachine.com/2011/06/running-transaction-test-killed/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Convert Epoch to date in log files</title>
		<link>http://partofthemachine.com/2011/04/convert-epoch-to-date-in-log-files/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=convert-epoch-to-date-in-log-files</link>
		<comments>http://partofthemachine.com/2011/04/convert-epoch-to-date-in-log-files/#comments</comments>
		<pubDate>Thu, 07 Apr 2011 15:44:15 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://partofthemachine.com/?p=24</guid>
		<description><![CDATA[Convert epoch to date all standard input files using perl one liner.]]></description>
			<content:encoded><![CDATA[<p>Ever had to go through a log file only to find timestamps are in epoch(unix) style format? Here&#8217;s a one liner that will convert them for you to review, without modifying the actual file:</p>
<blockquote><p><code>cat mylogfile | perl -ne 'if (/(\d{10})/){ my $epoch= $1; $date=scalar(localtime($epoch)); s/$epoch/$date/g; print; } else { print; }'</code></p></blockquote>
<p>It goes through all the input lines, finds a pattern of ten digits next to each other, and converts that to a date. The output could be much more nicer than this, but the one liner would be longer too. I like it because of its simplicity.</p>
]]></content:encoded>
			<wfw:commentRss>http://partofthemachine.com/2011/04/convert-epoch-to-date-in-log-files/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Mutt &#8211; Delete messages by date</title>
		<link>http://partofthemachine.com/2011/04/mutt-delete-messages-by-date/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=mutt-delete-messages-by-date</link>
		<comments>http://partofthemachine.com/2011/04/mutt-delete-messages-by-date/#comments</comments>
		<pubDate>Thu, 07 Apr 2011 14:05:58 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://partofthemachine.com/?p=16</guid>
		<description><![CDATA[Deleting old messages with Mutt, multiple mailboxes too.]]></description>
			<content:encoded><![CDATA[<p>Often you&#8217;ll have the need to perform an action that applies to multiple messages within a mailbox, and possibly multiple mailboxes to perform it in as well. Mutt is a great tool altogether, and the perfect tool for this job. If you want to, say, delete all messages older than 8 days, from the command line this will do the trick:</p>
<blockquote><p><code>#&gt; mutt -f Maildir -e 'push D~d&gt;8d\rq\n'</code></p></blockquote>
<p>If you have to do it on multiple mailboxes, it&#8217;s just as easy to wrap the command up in a loop:</p>
<blockquote><p><code>#&gt; for i in `ls -1 */Maildir`; do mutt -f $i -e 'push D~d&gt;8d\rq\n'; done</code></p></blockquote>
<p>Of course be careful with that &#8216;*&#8217;, it can be dangerous <img src='http://partofthemachine.com/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' />  Lots of more information here:</p>
<p>http://www.mutt.org/doc/manual/manual-4.html</p>
]]></content:encoded>
			<wfw:commentRss>http://partofthemachine.com/2011/04/mutt-delete-messages-by-date/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Unable to get webmail password</title>
		<link>http://partofthemachine.com/2010/10/unable-to-get-webmail-password/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=unable-to-get-webmail-password</link>
		<comments>http://partofthemachine.com/2010/10/unable-to-get-webmail-password/#comments</comments>
		<pubDate>Sun, 17 Oct 2010 18:02:55 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[plesk]]></category>
		<category><![CDATA[horde]]></category>
		<category><![CDATA[linux]]></category>

		<guid isPermaLink="false">http://partofthemachine.com/?p=5</guid>
		<description><![CDATA[Broken webmail access due to bad ownership/permissions on configuration files.]]></description>
			<content:encoded><![CDATA[<p>This error message shows when attempting to log in to Horde webmail in Plesk servers. The problem is a result of invalid permissions/ownership of the webmail credentials file. The solution is pretty simple, permissions of /etc/psa/.webmail.shadow need to be set in a very specific way:</p>
<p>Plesk 8.6.*:</p>
<blockquote><p><code># chmod 640 /etc/psa/.webmail.shadow<br />
# chown root:apache /etc/psa/.webmail.shadow</code></p></blockquote>
<p>Plesk 9.5.*:</p>
<blockquote><p><code># chmod 640 /etc/psa-webmail/horde/.horde.shadow<br />
# chown root:apache  /etc/psa-webmail/horde/.horde.shadow/code&gt;</code></p></blockquote>
<p>Webmail access should be restored once the changes have been made.</p>
]]></content:encoded>
			<wfw:commentRss>http://partofthemachine.com/2010/10/unable-to-get-webmail-password/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
