<?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>Backdrift &#187; bash</title>
	<atom:link href="http://backdrift.org/tag/bash/feed" rel="self" type="application/rss+xml" />
	<link>http://backdrift.org</link>
	<description></description>
	<lastBuildDate>Tue, 15 Nov 2011 03:01:58 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
		<item>
		<title>How To Create OOM Killer Exceptions in Linux</title>
		<link>http://backdrift.org/how-to-create-oom-killer-exceptions</link>
		<comments>http://backdrift.org/how-to-create-oom-killer-exceptions#comments</comments>
		<pubDate>Wed, 19 Oct 2011 18:59:21 +0000</pubDate>
		<dc:creator>Keith</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[bash]]></category>
		<category><![CDATA[cron]]></category>
		<category><![CDATA[Debian]]></category>
		<category><![CDATA[killer]]></category>
		<category><![CDATA[linux]]></category>
		<category><![CDATA[memory]]></category>
		<category><![CDATA[oom]]></category>
		<category><![CDATA[out of memory]]></category>
		<category><![CDATA[redhat]]></category>
		<category><![CDATA[scripting]]></category>
		<category><![CDATA[shell]]></category>
		<category><![CDATA[sysadmin]]></category>
		<category><![CDATA[troubleshooting]]></category>
		<category><![CDATA[ubuntu]]></category>
		<category><![CDATA[unix]]></category>

		<guid isPermaLink="false">http://backdrift.org/?p=1426</guid>
		<description><![CDATA[When a linux machine runs extremely low on memory the kernel begins deciding which processes it thinks are least important and starts killing them off in order to keep the processes it thinks are more important running. Unfortunately, the kernel OOM (out of memory) killer rarely makes the right decision, and your system is usually [...]]]></description>
		<wfw:commentRss>http://backdrift.org/how-to-create-oom-killer-exceptions/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Finding a MAC Address in VMware ESX</title>
		<link>http://backdrift.org/finding-a-mac-address-in-vmware-esx</link>
		<comments>http://backdrift.org/finding-a-mac-address-in-vmware-esx#comments</comments>
		<pubDate>Thu, 17 Feb 2011 00:07:35 +0000</pubDate>
		<dc:creator>Keith</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[address]]></category>
		<category><![CDATA[bash]]></category>
		<category><![CDATA[howto]]></category>
		<category><![CDATA[IP]]></category>
		<category><![CDATA[mac]]></category>
		<category><![CDATA[networking]]></category>
		<category><![CDATA[scripting]]></category>
		<category><![CDATA[sysadmin]]></category>
		<category><![CDATA[Virtualization]]></category>
		<category><![CDATA[vmware]]></category>

		<guid isPermaLink="false">http://backdrift.org/?p=918</guid>
		<description><![CDATA[Sometimes you just have to trace a system down by its MAC address. It could be a security incident, an abuse complaint or perhaps a long forgotten legacy system. Whatever it is, you don&#8217;t have much info to work with, but you do have a hardware address. Sadly, VMware doesn&#8217;t seem to have an easy [...]]]></description>
		<wfw:commentRss>http://backdrift.org/finding-a-mac-address-in-vmware-esx/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Automounting iSCSI with Autofs</title>
		<link>http://backdrift.org/automounting-iscsi-with-autofs</link>
		<comments>http://backdrift.org/automounting-iscsi-with-autofs#comments</comments>
		<pubDate>Thu, 06 May 2010 04:12:17 +0000</pubDate>
		<dc:creator>Keith</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[autofs]]></category>
		<category><![CDATA[automount]]></category>
		<category><![CDATA[backup]]></category>
		<category><![CDATA[bash]]></category>
		<category><![CDATA[equallogic]]></category>
		<category><![CDATA[ext3]]></category>
		<category><![CDATA[iSCSI]]></category>
		<category><![CDATA[linux]]></category>
		<category><![CDATA[san]]></category>
		<category><![CDATA[scripting]]></category>
		<category><![CDATA[storage]]></category>
		<category><![CDATA[sysadmin]]></category>

		<guid isPermaLink="false">http://backdrift.org/?p=498</guid>
		<description><![CDATA[I use SAN snapshots extensively to provide point-in-time recoverability for a number of different systems. This is a very reliable and efficient backup solution but it comes at the cost of additional complexity for individual file restoration. This is because the snapshot backups are of the entire volume and not each individual file. So when [...]]]></description>
		<wfw:commentRss>http://backdrift.org/automounting-iscsi-with-autofs/feed</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Printing the last occurrence of a string and everything below it with grep</title>
		<link>http://backdrift.org/printing-the-last-occurrance-of-a-string-and-everything-below-it-with-grep</link>
		<comments>http://backdrift.org/printing-the-last-occurrance-of-a-string-and-everything-below-it-with-grep#comments</comments>
		<pubDate>Thu, 28 Jan 2010 22:02:57 +0000</pubDate>
		<dc:creator>Keith</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[bash]]></category>
		<category><![CDATA[cat]]></category>
		<category><![CDATA[grep]]></category>
		<category><![CDATA[linux]]></category>
		<category><![CDATA[scripting]]></category>
		<category><![CDATA[sysadmin]]></category>
		<category><![CDATA[tac]]></category>
		<category><![CDATA[unix]]></category>

		<guid isPermaLink="false">http://backdrift.org/?p=303</guid>
		<description><![CDATA[So far the simplest way I&#8217;ve discovered to find the last occurrence of a string and print everything below it is with a combination of grep and tac (it&#8217;s cat backwards, get it?!). Say you want to find the last instance of foo and everything that came after it in a file. You could run [...]]]></description>
		<wfw:commentRss>http://backdrift.org/printing-the-last-occurrance-of-a-string-and-everything-below-it-with-grep/feed</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Logging bash history to syslog using traps</title>
		<link>http://backdrift.org/logging-bash-history-to-syslog-using-traps</link>
		<comments>http://backdrift.org/logging-bash-history-to-syslog-using-traps#comments</comments>
		<pubDate>Tue, 27 Oct 2009 19:08:43 +0000</pubDate>
		<dc:creator>Keith</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[bash]]></category>
		<category><![CDATA[linux]]></category>
		<category><![CDATA[sysadmin]]></category>
		<category><![CDATA[syslog]]></category>

		<guid isPermaLink="false">http://backdrift.org/?p=234</guid>
		<description><![CDATA[This is a handy way to log user&#8217;s bash histories to syslog without making any modifications to the bash source code itself. Simply drop the following snippet into either the per-user or system-wide bash profile (~/.bash_profile and /etc/profile, respectively) function log2syslog &#123; declare COMMAND COMMAND=$&#40;fc -ln -0&#41; logger -p local1.notice -t bash -i -- &#34;${USER}:${COMMAND}&#34; [...]]]></description>
		<wfw:commentRss>http://backdrift.org/logging-bash-history-to-syslog-using-traps/feed</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
	</channel>
</rss>
<!-- This Quick Cache file was built for (  backdrift.org/tag/bash/feed ) in 0.68200 seconds, on Feb 5th, 2012 at 1:46 pm UTC. -->
<!-- This Quick Cache file will automatically expire ( and be re-built automatically ) on Feb 5th, 2012 at 2:46 pm UTC -->
