<?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>Sun, 29 Aug 2010 20:41:40 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<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. [...]]]></description>
		<wfw:commentRss>http://backdrift.org/automounting-iscsi-with-autofs/feed</wfw:commentRss>
		<slash:comments>0</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>admin</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 [...]]]></description>
		<wfw:commentRss>http://backdrift.org/logging-bash-history-to-syslog-using-traps/feed</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>
