<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Check_ram on BAFM</title><link>https://christian.blog.pakiheim.de/tags/check_ram/</link><description>Recent content in Check_ram on BAFM</description><generator>Hugo -- 0.160.1</generator><language>en</language><lastBuildDate>Fri, 14 Nov 2008 18:08:30 +0000</lastBuildDate><atom:link href="https://christian.blog.pakiheim.de/tags/check_ram/index.xml" rel="self" type="application/rss+xml"/><item><title>Nagios and check_ram yet again</title><link>https://christian.blog.pakiheim.de/posts/2008-11-14_nagios-and-check-ram-yet-again/</link><pubDate>Fri, 14 Nov 2008 18:08:30 +0000</pubDate><guid isPermaLink="false">http://blog.barfoo.org/?p=1247</guid><description>&lt;p&gt;As some people know, I previously &amp;quot; &lt;em&gt;created&lt;/em&gt;&amp;quot; (mostly modified the check_swap plug-in to print RAM usage) check_ram in C. Now one of my problems for the past few months was putting the C plug-in as well as &amp;quot; &lt;em&gt;supported&lt;/em&gt;&amp;quot; environment under the same hat. Today I had another look at the amount of available plug-ins in &lt;a href="http://www.monitoringexchange.org/search?query=check_ram"&gt;NagiosExchange&lt;/a&gt;. There are quite a few plug-ins available, but as I do have some experience with Python, I used the one &lt;a href="http://www.monitoringexchange.org/inventory/Check-Plugins/Operating-Systems/Linux/Check_Ram-on-Linux-32-bit-and-64-bit-systems"&gt;written in Python&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;It was rather easy hacking in support for performance data into it, as the below shows. Someone else already posted a non-unified diff for performance data support, but that ain&amp;rsquo;t quite right according to the &lt;a href="http://nagiosplug.sourceforge.net/developer-guidelines.html#AEN203"&gt;Nagios plug-in development guidelines&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>Updated `check_ram' plugin</title><link>https://christian.blog.pakiheim.de/posts/2008-06-17_updated-check-ram-plugin/</link><pubDate>Tue, 17 Jun 2008 09:25:21 +0000</pubDate><guid isPermaLink="false">http://blog.barfoo.org/?p=358</guid><description>&lt;p&gt;As I was building the updated RPMs for SLES10, though needed to &lt;a href="https://christian.blog.pakiheim.de/uploads/2008/06/nagios-plugins-1412-check_ram.patch"&gt;refresh&lt;/a&gt; my old patch. Also, I was getting strange messages from autotools and fixed these &lt;a href="https://christian.blog.pakiheim.de/uploads/2008/06/nagios-plugins-1412-autoconf-quirks.patch"&gt;quirks&lt;/a&gt;, Now, I prepped a patch for it, and finished building new RPMs for i586 and x86_64.&lt;/p&gt;</description></item><item><title>Nagios undamp; plugins</title><link>https://christian.blog.pakiheim.de/posts/2007-10-06_nagios-amp-plugins/</link><pubDate>Sat, 06 Oct 2007 15:12:43 +0000</pubDate><guid isPermaLink="false">http://blog.barfoo.org/2007/10/06/nagios-plugins/</guid><description>&lt;p&gt;Since we started utilizing &lt;a href="http://www.nagios.org/"&gt;Nagios&lt;/a&gt;&amp;rsquo;s power two months ago, I finally came up with a C-based ram-plugin for nagios. The biggest problem I had with the python and perl based plugins, that some distributions (yes, SLES and Debian) don&amp;rsquo;t install either Python or Perl.&lt;/p&gt;
&lt;p&gt;Since I wanted a manageable setup (as in unified code base across all distributions), I wanted it to work without installing too much. So I took the &lt;a href="http://nagiosplug.svn.sourceforge.net/viewvc/nagiosplug/nagiosplug/trunk/plugins/check_swap.c?view=markup"&gt;swap plugin&lt;/a&gt; and basically removed what wasn&amp;rsquo;t necessary and &lt;a href="https://christian.blog.pakiheim.de/uploads/2007/10/check_ram.patch"&gt;voila&lt;/a&gt;!&lt;/p&gt;</description></item></channel></rss>