<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xml:base="http://www.johnandcailin.com" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
 <title>john quinn&#039;s blog</title>
 <link>http://www.johnandcailin.com/view/blog/john/linux</link>
 <description>john&#039;s blog entries</description>
 <language>en</language>
<item>
 <title>how to setup real-time email-notification for critical syslog events</title>
 <link>http://www.johnandcailin.com/blog/john/how-setup-real-time-email-notification-critical-syslog-events</link>
 <description>a few weeks ago, i wrote a &lt;a href=&quot;http://www.johnandcailin.com/blog/john/setting-syslog-distributed-application-logging&quot;&gt;short article&lt;/a&gt; about the advantages of using &lt;a href=&quot;http://en.wikipedia.org/wiki/Syslog&quot;&gt;syslog&lt;/a&gt; for all your logging needs. syslog is the standard logging solution for *nix platforms and integrates into virtually all application servers, network devices, and programming languages.

&lt;p&gt;it is often important for system administrators to get real time notification of critical events. unfortunately, it isn&#039;t immediately obvious how to do this in the syslog framework. in this article i show you step-by-step how to do this.
&lt;p&gt;&lt;a href=&quot;http://www.johnandcailin.com/blog/john/how-setup-real-time-email-notification-critical-syslog-events&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <comments>http://www.johnandcailin.com/blog/john/how-setup-real-time-email-notification-critical-syslog-events#comments</comments>
 <category domain="http://www.johnandcailin.com/category/blog-tags/debian">debian</category>
 <category domain="http://www.johnandcailin.com/category/blog-tags/linux">linux</category>
 <category domain="http://www.johnandcailin.com/category/blog-tags/syslog">syslog</category>
 <category domain="http://www.johnandcailin.com/category/blog-tags/tech">tech</category>
 <pubDate>Thu, 20 Dec 2007 07:11:10 -0800</pubDate>
 <dc:creator>john</dc:creator>
 <guid isPermaLink="false">262 at http://www.johnandcailin.com</guid>
</item>
<item>
 <title>using a guardian to ensure your lamp site is always up</title>
 <link>http://www.johnandcailin.com/blog/john/using-guardian-ensure-your-lamp-site-always</link>
 <description>&lt;a href=&quot;http://www.johnandcailin.com/blog/john/using-guardian-ensure-your-lamp-site-always&quot;&gt;&lt;img src=&quot;http://www.johnandcailin.com/files/images/drupalGuardian.smallish.jpg&quot; class=&quot;blog right&quot;&gt;&lt;/a&gt;

to guarantee maximum uptime for your site, it&#039;s a good idea to periodically check the health of your system and restart failing components. you can use a simple program to do this automatically. i like to call this type of program, a &quot;guardian&quot;.

&lt;p&gt;clearly guardians shouldn&#039;t be used as a crutch for a badly configured system. used appropriately, however,  they can decrease downtime due to unexpected events or administrator-error.

&lt;p&gt;in this article, i describe how to implement, install and configure a guardian using a lightweight bash script. i go on to describe how to watch over your lamp install using this guardian. please note that all code and configurations have been tested on debian etch but should be useful for other *nix flavors with subtle modifications.
&lt;p&gt;&lt;a href=&quot;http://www.johnandcailin.com/blog/john/using-guardian-ensure-your-lamp-site-always&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <comments>http://www.johnandcailin.com/blog/john/using-guardian-ensure-your-lamp-site-always#comments</comments>
 <category domain="http://www.johnandcailin.com/category/blog-tags/apache">apache</category>
 <category domain="http://www.johnandcailin.com/category/blog-tags/drupal">drupal</category>
 <category domain="http://www.johnandcailin.com/category/blog-tags/linux">linux</category>
 <category domain="http://www.johnandcailin.com/category/blog-tags/mysql">mysql</category>
 <category domain="http://www.johnandcailin.com/category/blog-tags/tech">tech</category>
 <pubDate>Tue, 18 Dec 2007 11:02:55 -0800</pubDate>
 <dc:creator>john</dc:creator>
 <guid isPermaLink="false">242 at http://www.johnandcailin.com</guid>
</item>
<item>
 <title>setting up syslog for distributed application logging</title>
 <link>http://www.johnandcailin.com/blog/john/setting-syslog-distributed-application-logging</link>
 <description>as you probably know, &lt;a href=&quot;http://en.wikipedia.org/wiki/Syslog&quot;&gt;syslog&lt;/a&gt; is a *nix logging subsystem, typically used for system logging and kernel message trapping. you might not know that it&#039;s also an good tool for application logging, including large distributed systems. it has been around since the dawn of time and has very broad language, application and device support. here&#039;s a quick how-to to get you started, with debian etch examples.&lt;p&gt;&lt;a href=&quot;http://www.johnandcailin.com/blog/john/setting-syslog-distributed-application-logging&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <comments>http://www.johnandcailin.com/blog/john/setting-syslog-distributed-application-logging#comments</comments>
 <category domain="http://www.johnandcailin.com/category/blog-tags/debian">debian</category>
 <category domain="http://www.johnandcailin.com/category/blog-tags/linux">linux</category>
 <category domain="http://www.johnandcailin.com/category/blog-tags/syslog">syslog</category>
 <category domain="http://www.johnandcailin.com/category/blog-tags/tech">tech</category>
 <pubDate>Tue, 09 Oct 2007 12:14:01 -0700</pubDate>
 <dc:creator>john</dc:creator>
 <guid isPermaLink="false">70 at http://www.johnandcailin.com</guid>
</item>
</channel>
</rss>
