[BACK]Return to index.html CVS log [TXT][DIR] Up to [local] / nagios / check_hw_sensors

Diff for /nagios/check_hw_sensors/index.html between version 1.4 and 1.7

version 1.4, 2006/10/26 00:30:23 version 1.7, 2008/03/10 17:31:12
Line 1 
Line 1 
 <html><head><title>Nagios Check - check_hw_sensors</title></head>  <html><head><title>Nagios Check - check_hw_sensors</title></head>
     <body>      <body>
         <h1>Nagios Check - check_hw_sensors</h1>          <h1>Nagios Check - check_hw_sensors</h1>
         <p>check_hw_sensors plugin for Nagios monitors sysctl hw.sensors on OpenBSD</p>          <p>check_hw_sensors plugin for Nagios monitors sysctl hw.sensors on OpenBSD</p>
         <p>With the new sensor framework in OpenBSD 3.9, I wanted to be able to monitor the new hw.sensors from <a href='http://www.nagios.org/'>Nagios</a> and this is what I have.  The documentation is a bit thin and I don't know how reliable it is.  I would be happy to accept patches.  Send them to <a href='mailto:andrew+nagios@rraz.net'>andrew+nagios@rraz.net</a>.  I know the docs aren't as good as I would like, so if there are places that need clarification, please let me know!</p>          <p>With the new sensor framework in OpenBSD 3.9, I wanted to be able to monitor the new hw.sensors from <a href='http://www.nagios.org/'>Nagios</a> and this is what I have.  The documentation is a bit thin and I don't know how reliable it is.  I would be happy to accept patches.  Send them to <a href='mailto:andrew+nagios@rraz.net'>andrew+nagios@rraz.net</a>.  I know the docs aren't as good as I would like, so if there are places that need clarification, please let me know!</p>
                 <p>New in this release is the ability to check the sensors that report their status.  Since many sensors support this, it can make the size of your sensorsd.conf much smaller.  For example, check_hw_sensors will automatically check these two sensors:                  <p>New in this release is support for the new 2 level sensors in OpenBSD 4.0-current.  They seem way more better, and I may change some stuff to only support that version after I get all my machines moved to 4.1.</p>
                 <ul>                  <p>They changed the output again, so 1.23 is an update to fix that.</p>
                         <li>hw.sensors.76=esm0, Fan 4, OK, fanrpm, 3629 RPM</li>                  <p>It has the ability to check the sensors that report their status.  Since many sensors support this, it can make the size of your sensorsd.conf much smaller.  For example, check_hw_sensors will automatically check these two sensors:
                         <li>hw.sensors.77=esm0, Fan 5, CRITICAL, fanrpm, 0 RPM</li>                  <ul>
                 </ul>                          <li>hw.sensors.76=esm0, Fan 4, 3629 RPM, OK</li>
                 It will report the status listed to Nagios.  For 76, it would be OK, for 77 it would be CRITICAL.  You don't need to put anything in a config file to support those.</p>                          <li>hw.sensors.77=esm0, Fan 5, 0 RPM, CRITICAL</li>
         <p>What I think is really kewl about this plugin is that it can use the same sensorsd.conf as sensorsd.  That means that they can be easily kept in sync.  But, since Nagios supports both warning and critical alerts, it turned out really handy that sensorsd ignores any additional capabilities in the file.  The addtional capabilities check_hw_sensors supports are described below.  If you have an /etc/sensorsd.conf with the checks you want, it can be run as simply as 'check_hw_sensors -f'.  If you only want to check the sensors that report their status, you can ever run it as just 'check_hw_sensors'.</p>                  </ul>
         <p>TODO:                  It will report the status listed to Nagios.  For 76, it would be OK, for 77 it would be CRITICAL.  You don't need to put anything in a config file to support those.</p>
         <ul>          <p>What I think is really kewl about this plugin is that it can use the same sensorsd.conf as sensorsd.  That means that they can be easily kept in sync.  But, since Nagios supports both warning and critical alerts, it turned out really handy that sensorsd ignores any additional capabilities in the file.  The addtional capabilities check_hw_sensors supports are described below.  If you have an /etc/sensorsd.conf with the checks you want, it can be run as simply as 'check_hw_sensors -f'.  If you only want to check the sensors that report their status, you can ever run it as just 'check_hw_sensors'.</p>
             <li>need real documentation.</li>          <p>TODO:
                         <li>the RANGE using the colon to separate probably screws up the getcap of sensorsd.conf, so it should probably get replaced with a dash or somesuch</li>          <ul>
         </ul>              <li>need real documentation.</li>
         </p>                          <li>the RANGE using the colon to separate probably screws up the getcap of sensorsd.conf, so it should probably get replaced with a dash or somesuch</li>
         <p><center><b><a href='check_hw_sensors-1.17.tar.gz'>Download the current version here</a></b></center></p>          </ul>
         <h4>          </p>
           Please be sure to support the <a href="http://www.openbsd.org">OpenBSD</a>          <p><center><b><a href='check_hw_sensors-1.25.tar.gz'>Download the current version here</a></b></center></p>
           project by purchasing          <h4>
           <a href="http://www.openbsd.org/items.html">CDs</a>,            Please be sure to support the <a href="http://www.openbsd.org">OpenBSD</a>
           <a href="http://www.openbsd.org/tshirts.html">T-shirts</a>, or making a            project by purchasing
           <a href="http://www.openbsd.org/donations.html">donation</a>.            <a href="http://www.openbsd.org/items.html">CDs</a>,
           <br />            <a href="http://www.openbsd.org/tshirts.html">T-shirts</a>, or making a
           These finances ensure that OpenBSD will continue to exist, and            <a href="http://www.openbsd.org/donations.html">donation</a>.
           will remain <a href="http://www.openbsd.org/policy.html">free</a>            <br />
           for everyone to use and reuse as they see fit.            These finances ensure that OpenBSD will continue to exist, and
         </h4>            will remain <a href="http://www.openbsd.org/policy.html">free</a>
         <pre>            for everyone to use and reuse as they see fit.
     check_hw_sensors [-i] (-f [&lt;FILENAME&gt;]|(-s &lt;hw.sensors id&gt; [-w limit] [-c limit]))          </h4>
           <pre>
 Usage:      check_hw_sensors [-i] (-f [&lt;FILENAME&gt;]|(-s &lt;hw.sensors id&gt; [-w limit] [-c limit]))
     -i, --ignore-status  
         Don't check the status of sensors that report it.  Usage:
     -f, --filename=FILE      -i, --ignore-status
         FILE to load checks from (defaults to /etc/sensorsd.conf)          Don't check the status of sensors that report it.
     -s, --sensor=ID      -f, --filename=FILE
         ID of a single sensor.  "-s 0" means hw.sensors.0.          FILE to load checks from (defaults to /etc/sensorsd.conf)
     -w, --warning=RANGE or single ENTRY      -s, --sensor=ID
         Exit with WARNING status if outside of RANGE or if != ENTRY          ID of a single sensor.  "-s 0" means hw.sensors.0.
     -c, --critical=RANGE or single ENTRY      -w, --warning=RANGE or single ENTRY
         Exit with CRITICAL status if outside of RANGE or if != ENTRY          Exit with WARNING status if outside of RANGE or if != ENTRY
         </pre>      -c, --critical=RANGE or single ENTRY
         <p>FILE is in the same format as <a href='http://www.openbsd.org/cgi-bin/man.cgi?query=sensorsd.conf'>sensorsd.conf(5)</a> plus some additional entries.  These additional entries in the file are ignored by <a href='http://www.openbsd.org/cgi-bin/man.cgi?query=sensorsd'>sensorsd(8)</a>.  </p>          Exit with CRITICAL status if outside of RANGE or if != ENTRY
           </pre>
         <p>check_hw_sensors understands the following entries:<br>          <p>FILE is in the same format as <a href='http://www.openbsd.org/cgi-bin/man.cgi?query=sensorsd.conf'>sensorsd.conf(5)</a> plus some additional entries.  These additional entries in the file are ignored by <a href='http://www.openbsd.org/cgi-bin/man.cgi?query=sensorsd'>sensorsd(8)</a>.  </p>
                 low, high, crit, warn, crit.low, crit.high, warn.low, warn.high,  
                 ignore, status</p>          <p>check_hw_sensors understands the following entries:<br>
                   low, high, crit, warn, crit.low, crit.high, warn.low, warn.high,
         <p>An ENTRY depends on the type.  The descriptions in <a href='http://www.openbsd.org/cgi-bin/man.cgi?query=sensorsd.conf'>sensorsd.conf(5)</a>                  ignore, status</p>
         can be used when appropriate, or you can use the following:  
           <p>An ENTRY depends on the type.  The descriptions in <a href='http://www.openbsd.org/cgi-bin/man.cgi?query=sensorsd.conf'>sensorsd.conf(5)</a>
         <ul>          can be used when appropriate, or you can use the following:
             <li>volts_dc, fanrpm or raw<br>  
             Anything that includes digits.          <ul>
             Both the value of the check and the value of the sensor              <li>fanrpm, volts_dc, amps, watthour, amphour, integer (raw), percent, lux or timedelta<br>
             response that are not either a digit or period are stripped              Anything that includes digits.
             and then the two resultant values are compared.</li>              Both the value of the check and the value of the sensor
               response that are not either a digit or period are stripped
             <li>temp<br>              and then the two resultant values are compared.</li>
             Can be as above, but if the entry has an F in it,  
             it compares farenheit, otherwise it uses celcius.</li>              <li>temp<br>
               Can be as above, but if the entry has an F in it,
             <li>indicator or drive<br>              it compares farenheit, otherwise it uses celcius.</li>
             does a case sensitive match of each  
             entry in the comma separated list and if it does not match              <li>indicator or drive<br>
             any of the entries, it matches the status.  Does not support any low or high entries.</li>              does a case sensitive match of each
         </ul>              entry in the comma separated list and if it does not match
               any of the entries, it sets the status.</li>
         <p>The entries 'crit' or 'warn' (or the -c or -w on the command line)          </ul>
         may be a RANGE or a comma separated list of acceptable values.  
         The comma separated list of values contains a list of things that          <p>The entries 'crit' or 'warn' (or the -c or -w on the command line)
         will NOT cause the status.  This is possibly counterintuitive, but          may be a RANGE or a comma separated list of acceptable values.
         you are more likely to know good values than bad values.</p>          The comma separated list of values contains a list of things that
           will NOT cause the status.  This is possibly counterintuitive, but
         <p>A RANGE is a low ENTRY and a high ENTRY separated by a colon (:).          you are more likely to know good values than bad values.</p>
         It can also be low: or :high with the other side left blank to only  
         make the single check..<p>          <p>A RANGE is a low ENTRY and a high ENTRY separated by a colon (:).
           It can also be low: or :high with the other side left blank to only
                 <p>An entry marked "ignore" will cause that sensor to be skipped.          make the single check..<p>
                 Generally used with status checking of all sensors to ignore sensors you  
                 don't care about or that report incorrectly.</p>                  <p>An entry marked "ignore" will cause that sensor to be skipped.
                   Generally used with status checking of all sensors to ignore sensors you
                 <p>If you are using --ignore-status, you can still check the status of                  don't care about or that report incorrectly.</p>
                 individual sensors with a status entry.</p>  
                   <p>If you are using --ignore-status, you can still check the status of
         <p>check_hw_sensors (nagios-plugins 1.4.2) 1.17<br>                  individual sensors with a status entry.</p>
         The nagios plugins come with ABSOLUTELY NO WARRANTY. You may redistribute  
         copies of the plugins under the terms of the GNU General Public License.          <p>check_hw_sensors (nagios-plugins 1.4.2) 1.22<br>
         For more information about these matters, see the file named COPYING.</p>          The nagios plugins come with ABSOLUTELY NO WARRANTY. You may redistribute
           copies of the plugins under the terms of the GNU General Public License.
         <h3>Example sensorsd.conf</h3>          For more information about these matters, see the file named COPYING.</p>
         <pre>  
 # hw.sensors.3=esm0, Ambient, OK, temp, 21.50 degC / 70.70 degF          <h3>Example sensorsd.conf</h3>
 hw.sensors.3:high=28C:warn.high=25C          <pre>
   # hw.sensors.acpibat0.volt0=7.40 V DC, (voltage), OK
 # hw.sensors.12=esm0, Chassis Intrusion, indicator, Off  # hw.sensors.acpibat0.volt1=8.30 V DC, (current voltage), OK
 hw.sensors.12:warn=Off  # hw.sensors.acpibat0.watthour0=57.72 Wh, (last full capacity)
   # hw.sensors.acpibat0.watthour1=0.00 Wh, (warning capacity)
 # hw.sensors.29=esm0, Drive 0, drive, online  # hw.sensors.acpibat0.watthour2=0.12 Wh, (low capacity)
 hw.sensors.29:crit=online  # hw.sensors.acpibat0.watthour3=57.72 Wh, (remaining capacity)
 # hw.sensors.30=esm0, Drive 1, drive, online  hw.sensors.acpibat0.watthour3:warn.low=50 Wh:crit.low=30 Wh
 hw.sensors.30:crit=online  # hw.sensors.acpibat0.raw0=2, (battery charging), OK
 # hw.sensors.31=esm0, Drive 2, drive, unknown  # hw.sensors.acpibat0.raw1=99, (rate)
 # hw.sensors.32=esm0, Drive 3, drive, unknown  # hw.sensors.acpiac0.indicator0=On, (power supply)
 # hw.sensors.33=esm0, Drive 4, drive, online  hw.sensors.acpiac0.indicator0:crit=On
 hw.sensors.33:crit=online  # hw.sensors.acpitz0.temp0=62.95 degC, (zone temperature)
 # hw.sensors.34=esm0, Drive 5, drive, online  hw.sensors.acpitz0.temp0:warn.high=65 degC:crit.high=75 degC
 hw.sensors.34:crit=online          </pre>
 # hw.sensors.35=esm0, Drive 6, drive, unknown                  <h3>CVS log for check_hw_sensors</h3>
 # hw.sensors.36=esm0, Drive 7, drive, unknown                  <pre>
   RCS file: /cvs/scripts/Admin scripts/check_hw_sensors/check_hw_sensors,v
 # hw.sensors.70=esm0, Power Supply 1 AC, indicator, On  Working file: check_hw_sensors
 hw.sensors.70:crit=On  head: 1.25
 # hw.sensors.71=esm0, Power Supply 1 SW, indicator, On  branch:
 hw.sensors.71:crit=On  locks: strict
 # hw.sensors.72=esm0, Power Supply 1 OK, indicator, On  access list:
 hw.sensors.72:crit=On  symbolic names:
 # hw.sensors.74=esm0, Power Supply 1 FFAN, indicator, Off  keyword substitution: kv
 hw.sensors.74:crit=Off  total revisions: 25;    selected revisions: 25
 # hw.sensors.75=esm0, Power Supply 1 OTMP, indicator, Off  description:
 hw.sensors.75:crit=Off  ----------------------------
   revision 1.25
 # hw.sensors.76=esm0, Power Supply 2 AC, indicator, On  date: 2008/03/10 16:21:53;  author: andrew;  state: Exp;  lines: +5 -5
 hw.sensors.76:crit=On  Fix it for sensors with more than 1 digit at the end.
 # hw.sensors.77=esm0, Power Supply 2 SW, indicator, On  ----------------------------
 hw.sensors.77:crit=On  revision 1.24
 # hw.sensors.78=esm0, Power Supply 2 OK, indicator, On  date: 2007/02/14 21:59:10;  author: andrew;  state: Exp;  lines: +5 -4
 hw.sensors.78:crit=On  Add an idea to the TODO list.
 # hw.sensors.80=esm0, Power Supply 2 FFAN, indicator, Off  ----------------------------
 hw.sensors.80:crit=Off  revision 1.23
 # hw.sensors.81=esm0, Power Supply 2 OTMP, indicator, Off  date: 2007/01/22 02:38:35;  author: andrew;  state: Exp;  lines: +8 -5
 hw.sensors.81:crit=Off  again they change the output!
   ----------------------------
 # hw.sensors.82=esm0, Power Supply 3 AC, indicator, On  revision 1.22
 hw.sensors.82:crit=On  date: 2007/01/06 03:16:41;  author: andrew;  state: Exp;  lines: +11 -4
 # hw.sensors.83=esm0, Power Supply 3 SW, indicator, On  Support the new dual level sensors
 hw.sensors.83:crit=On  ----------------------------
 # hw.sensors.84=esm0, Power Supply 3 OK, indicator, On  revision 1.21
 hw.sensors.84:crit=On  date: 2006/12/05 16:26:27;  author: andrew;  state: Exp;  lines: +5 -5
 # hw.sensors.86=esm0, Power Supply 3 FFAN, indicator, Off  new better example for 4.0
 hw.sensors.86:crit=Off  and fix the s/drive\s// from the data, not the type
 # hw.sensors.87=esm0, Power Supply 3 OTMP, indicator, Off  ----------------------------
 hw.sensors.87:crit=Off  revision 1.20
   date: 2006/12/05 00:17:47;  author: andrew;  state: Exp;  lines: +35 -26
 # hw.sensors.88=esm0, Fan 1, CRITICAL, fanrpm, 0 RPM  Match sensors differently depending on OS Version from the Config module.
 hw.sensors.88:ignore  
 # hw.sensors.89=esm0, Fan 2, CRITICAL, fanrpm, 0 RPM  Also support checks on the other sensor types and document that.
 hw.sensors.89:ignore  
 # hw.sensors.90=esm0, Fan 3, CRITICAL, fanrpm, 0 RPM  and refactor the way I return a $sensor-&gt;{'status'} from ~10 lines to 1.
 hw.sensors.90:ignore  ----------------------------
 # hw.sensors.91=esm0, Fan 4, CRITICAL, fanrpm, 0 RPM  revision 1.19
 hw.sensors.91:ignore  date: 2006/12/04 23:33:53;  author: andrew;  state: Exp;  lines: +8 -3
 # hw.sensors.92=esm0, Fan 5, CRITICAL, fanrpm, 0 RPM  add a regex for the 'percent' type of sensor
 hw.sensors.92:ignore  ----------------------------
 # hw.sensors.93=esm0, Fan 6, CRITICAL, fanrpm, 0 RPM  revision 1.18
 hw.sensors.93:ignore  date: 2006/12/02 02:15:17;  author: andrew;  state: Exp;  lines: +74 -9
         </pre>  fix it for the output from OpenBSD 4.0
         <h3>Example output from sysctl hw.sensors from that box</h3>  ----------------------------
         <pre>  revision 1.17
 hw.sensors.0=esm0, CPU 1, OK, temp, 36.00 degC / 96.80 degF  date: 2006/10/25 23:30:23;  author: andrew;  state: Exp;  lines: +4 -7
 hw.sensors.1=esm0, CPU 2, OK, temp, 41.00 degC / 105.80 degF  get the docs up to match the new version
 hw.sensors.2=esm0, Mainboard, OK, temp, 28.00 degC / 82.40 degF  ----------------------------
 hw.sensors.3=esm0, Ambient, OK, temp, 21.50 degC / 70.70 degF  revision 1.16
 hw.sensors.4=esm0, CPU 1 Core, OK, volts_dc, 1.65 V  date: 2006/10/25 18:36:46;  author: andrew;  state: Exp;  lines: +4 -4
 hw.sensors.5=esm0, CPU 2 Core, OK, volts_dc, 1.67 V  Stuff in CVS should output nagios format
 hw.sensors.6=esm0, Motherboard +5V, OK, volts_dc, 4.98 V  ----------------------------
 hw.sensors.7=esm0, Motherboard +12V, OK, volts_dc, 11.97 V  revision 1.15
 hw.sensors.8=esm0, Motherboard +3.3V, OK, volts_dc, 3.25 V  date: 2006/10/25 18:35:59;  author: andrew;  state: Exp;  lines: +73 -46
 hw.sensors.9=esm0, Motherboard +2.5V, OK, volts_dc, 2.49 V  add support for the status as reported by the sensors.  it is teh r0x0r!
 hw.sensors.10=esm0, Motherboard GTL Term, OK, volts_dc, 1.50 V  ----------------------------
 hw.sensors.11=esm0, Motherboard Battery, OK, volts_dc, 2.92 V  revision 1.14
 hw.sensors.12=esm0, Chassis Intrusion, indicator, Off  date: 2006/05/04 01:30:29;  author: andrew;  state: Exp;  lines: +6 -4
 hw.sensors.13=esm0, Chassis Fan Ctrl, raw, 2  I thought I checked this in already
 hw.sensors.14=esm0, Fan 1, OK, fanrpm, 3839 RPM  ----------------------------
 hw.sensors.15=esm0, Fan 2, OK, fanrpm, 4040 RPM  revision 1.13
 hw.sensors.16=esm0, Backplane Control, raw, 227  date: 2006/05/03 22:16:42;  author: andrew;  state: Exp;  lines: +7 -6
 hw.sensors.17=esm0, Backplane Top, OK, temp, 30.00 degC / 86.00 degF  Some more fixing of the help
 hw.sensors.18=esm0, Backplane Bottom, OK, temp, 29.50 degC / 85.10 degF  ----------------------------
 hw.sensors.19=esm0, Backplane +5V, OK, volts_dc, 4.97 V  revision 1.12
 hw.sensors.20=esm0, Backplane +12V, OK, volts_dc, 12.06 V  date: 2006/05/03 21:54:43;  author: andrew;  state: Exp;  lines: +51 -30
 hw.sensors.21=esm0, Backplane Board, OK, volts_dc, 2.83 V  Get the help output cleaned up.  Still not 100% what I want, but so far so good.
 hw.sensors.22=esm0, Backplane Fan Control, raw, 8738  ----------------------------
 hw.sensors.23=esm0, Backplane Fan 1, OK, fanrpm, 3690 RPM  revision 1.11
 hw.sensors.24=esm0, Backplane Fan 2, OK, fanrpm, 3552 RPM  date: 2006/05/03 20:01:09;  author: holligan;  state: Exp;  lines: +4 -4
 hw.sensors.25=esm0, Backplane Fan 3, OK, fanrpm, 3505 RPM  updated and clarified help
 hw.sensors.26=esm0, Backplane SCSI A Connected, indicator, On  ----------------------------
 hw.sensors.27=esm0, Backplane SCSI A External, OK, volts_dc, 4.68 V  revision 1.10
 hw.sensors.28=esm0, Backplane SCSI A Internal, OK, volts_dc, 4.79 V  date: 2006/05/03 03:31:22;  author: andrew;  state: Exp;  lines: +27 -42
 hw.sensors.29=esm0, Drive 0, drive, online  A bunch of cleanup and some kewl refactoring into loops.
 hw.sensors.30=esm0, Drive 1, drive, online  
 hw.sensors.31=esm0, Drive 2, drive, unknown  Still need to find a way to refactor the checks that are so similar!
 hw.sensors.32=esm0, Drive 3, drive, unknown  ----------------------------
 hw.sensors.33=esm0, Drive 4, drive, online  revision 1.9
 hw.sensors.34=esm0, Drive 5, drive, online  date: 2006/05/03 02:26:47;  author: andrew;  state: Exp;  lines: +8 -8
 hw.sensors.35=esm0, Drive 6, drive, unknown  It now doesn't do nonexistent checks (for some stuff anyway)
 hw.sensors.36=esm0, Drive 7, drive, unknown  Also changed the &lt;br /&gt; to &lt;br&gt;.  Not valid XHTML whatever, but it does get stripped before getting sent to my pager.
 hw.sensors.37=esm0, Power Supply 1 +5V, volts_dc, 5.07 V  ----------------------------
 hw.sensors.38=esm0, Power Supply 1 +12V, volts_dc, 12.13 V  revision 1.8
 hw.sensors.39=esm0, Power Supply 1 +3.3V, volts_dc, 3.32 V  date: 2006/05/02 21:23:29;  author: andrew;  state: Exp;  lines: +6 -16
 hw.sensors.40=esm0, Power Supply 1 -5V, volts_dc, 5.08 V  Better looking output for the web page.
 hw.sensors.41=esm0, Power Supply 1 -12V, volts_dc, 12.20 V  ----------------------------
 hw.sensors.42=esm0, Power Supply 2 +5V, volts_dc, 5.09 V  revision 1.7
 hw.sensors.43=esm0, Power Supply 2 +12V, volts_dc, 12.08 V  date: 2006/05/02 20:03:53;  author: andrew;  state: Exp;  lines: +5 -5
 hw.sensors.44=esm0, Power Supply 2 +3.3V, volts_dc, 3.34 V  oops, that's an array ref!
 hw.sensors.45=esm0, Power Supply 2 -5V, volts_dc, 5.01 V  ----------------------------
 hw.sensors.46=esm0, Power Supply 2 -12V, volts_dc, 12.03 V  revision 1.6
 hw.sensors.47=esm0, Power Supply 3 +5V, volts_dc, 5.03 V  date: 2006/05/02 19:59:47;  author: andrew;  state: Exp;  lines: +7 -5
 hw.sensors.48=esm0, Power Supply 3 +12V, volts_dc, 12.15 V  Better output for the OK checks
 hw.sensors.49=esm0, Power Supply 3 +3.3V, volts_dc, 3.34 V  ----------------------------
 hw.sensors.50=esm0, Power Supply 3 -5V, volts_dc, 5.03 V  revision 1.5
 hw.sensors.51=esm0, Power Supply 3 -12V, volts_dc, 11.97 V  date: 2006/05/02 19:49:29;  author: andrew;  state: Exp;  lines: +19 -12
 hw.sensors.52=esm0, System Power Supply +5V, volts_dc, 5.02 V  Only show details for things other than OK, cuZ we are limited in the amount of data we can return :-(
 hw.sensors.53=esm0, System Power Supply +12V, volts_dc, 12.09 V  ----------------------------
 hw.sensors.54=esm0, System Power Supply +3.3V, volts_dc, 3.32 V  revision 1.4
 hw.sensors.55=esm0, System Power Supply -5V, volts_dc, 4.91 V  date: 2006/05/02 15:54:42;  author: andrew;  state: Exp;  lines: +44 -21
 hw.sensors.56=esm0, System Power Supply -12V, volts_dc, 11.82 V  Some cleanup, as well as making it output a single line like nagios supposedly likes.
 hw.sensors.57=esm0, System Power Supply +5V aux, volts_dc, 5.16 V  ----------------------------
 hw.sensors.58=esm0, Power Supply 1 +5V, OK, amps, 2.40 A  revision 1.3
 hw.sensors.59=esm0, Power Supply 1 +12V, OK, amps, 1.00 A  date: 2006/05/02 01:39:23;  author: andrew;  state: Exp;  lines: +3 -3
 hw.sensors.60=esm0, Power Supply 1 +3.3V, OK, amps, 1.80 A  fix the help getopts.
 hw.sensors.61=esm0, Power Supply 2 +5V, OK, amps, 2.80 A  ----------------------------
 hw.sensors.62=esm0, Power Supply 2 +12V, OK, amps, 1.20 A  revision 1.2
 hw.sensors.63=esm0, Power Supply 2 +3.3V, OK, amps, 1.60 A  date: 2006/05/02 01:29:33;  author: andrew;  state: Exp;  lines: +427 -11
 hw.sensors.64=esm0, Power Supply 3 +5V, OK, amps, 1.20 A  Adding the sensors from one of the routers, cuZ there were a lot and I can use it for testing.
 hw.sensors.65=esm0, Power Supply 3 +12V, OK, amps, 1.00 A  
 hw.sensors.66=esm0, Power Supply 3 +3.3V, OK, amps, 1.60 A  Also, now the check_hw_sensors now seems to be OK.  I need to put it on a few machines and set up the checks now.  If it works for the rest of the week, I can clean it up and mebbe put it on teh interweb and post to undeadly.
 hw.sensors.67=esm0, Power Supply 1 Fan, OK, fanrpm, 3726 RPM  ----------------------------
 hw.sensors.68=esm0, Power Supply 2 Fan, OK, fanrpm, 4042 RPM  revision 1.1
 hw.sensors.69=esm0, Power Supply 3 Fan, OK, fanrpm, 3606 RPM  date: 2006/05/01 18:11:23;  author: andrew;  state: Exp;
 hw.sensors.70=esm0, Power Supply 1 AC, indicator, On  add this so I can check it out on a box for testing
 hw.sensors.71=esm0, Power Supply 1 SW, indicator, On  =============================================================================
 hw.sensors.72=esm0, Power Supply 1 OK, indicator, On                  </pre>
 hw.sensors.73=esm0, Power Supply 1 ON, OK, indicator, On          <p>Andrew Fresh &lt;<a href='mailto:andrew@mad-techies.org'>andrew@mad-techies.org</a>&gt;</p>
 hw.sensors.74=esm0, Power Supply 1 FFAN, indicator, Off          <p><small>$RedRiver: index.html,v 1.6 2007/01/06 03:27:53 andrew Exp $</small></p>
 hw.sensors.75=esm0, Power Supply 1 OTMP, indicator, Off      </body>
 hw.sensors.76=esm0, Power Supply 2 AC, indicator, On  </html>
 hw.sensors.77=esm0, Power Supply 2 SW, indicator, On  
 hw.sensors.78=esm0, Power Supply 2 OK, indicator, On  
 hw.sensors.79=esm0, Power Supply 2 ON, OK, indicator, On  
 hw.sensors.80=esm0, Power Supply 2 FFAN, indicator, Off  
 hw.sensors.81=esm0, Power Supply 2 OTMP, indicator, Off  
 hw.sensors.82=esm0, Power Supply 3 AC, indicator, On  
 hw.sensors.83=esm0, Power Supply 3 SW, indicator, On  
 hw.sensors.84=esm0, Power Supply 3 OK, indicator, On  
 hw.sensors.85=esm0, Power Supply 3 ON, OK, indicator, On  
 hw.sensors.86=esm0, Power Supply 3 FFAN, indicator, Off  
 hw.sensors.87=esm0, Power Supply 3 OTMP, indicator, Off  
 hw.sensors.88=esm0, Fan 1, CRITICAL, fanrpm, 0 RPM  
 hw.sensors.89=esm0, Fan 2, CRITICAL, fanrpm, 0 RPM  
 hw.sensors.90=esm0, Fan 3, CRITICAL, fanrpm, 0 RPM  
 hw.sensors.91=esm0, Fan 4, CRITICAL, fanrpm, 0 RPM  
 hw.sensors.92=esm0, Fan 5, CRITICAL, fanrpm, 0 RPM  
 hw.sensors.93=esm0, Fan 6, CRITICAL, fanrpm, 0 RPM  
 hw.sensors.94=esm0, Fan Enclosure, raw, 42498  
 hw.sensors.95=safte0, fan0, OK, indicator, On  
 hw.sensors.96=safte0, fan1, OK, indicator, On  
 hw.sensors.97=safte0, fan2, OK, indicator, On  
 hw.sensors.98=safte0, temp0, OK, temp, 30.00 degC / 86.00 degF  
 hw.sensors.99=safte0, temp1, OK, temp, 29.44 degC / 85.00 degF  
         </pre>  
         <p>Andrew Fresh &lt;<a href='mailto:andrew@mad-techies.org'>andrew@mad-techies.org</a>&gt;</p>  
         <p><small>$RedRiver: index.html,v 1.3 2006/05/04 01:39:16 andrew Exp $</small></p>  
     </body>  
 </html>  

Legend:
Removed from v.1.4  
changed lines
  Added in v.1.7

FreeBSD-CVSweb <freebsd-cvsweb@FreeBSD.org>