Using the joystick for monitoring closures

[Rob Enders]

Hi all.. I have been a user of Nagios right back to the Netsaint 1.0 days. I
needed a way to monitor several external contact closures generated by
external equipment, (We are a radio station and use audio silence monitors
that give a closure on alarm). I came across some software by Christian
Garbs called joyd. http://www.cgarbs.de/joyd.en.html  It is a daemon that
can monitor the joystick port typically found on audio cards. It will
execute a command based on the change in state of the joystick buttons
and/or the position of the handle. It was a simple matter to add the
necessary info for the submit_check_result script that Ethan Galstad
suggests in the nagios docs. This functions similar to the NRPE software and
other passive plugins. It will send a command for the original closure as
well as the release. The development version includes the features
described.. I am using this with two separate gameports in order to get
enough closures, but the software supports thresholds on the joystick handle
position which could be used for additional closures. 
 
Hopefully someone will find this info useful..
 
Ciao
 
Rob Enders
CKNX Radio
Wingham, ON Canada
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.monitoring-lists.org/archive/users/attachments/20070725/e1f88240/attachment.html>
-------------- next part --------------
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
-------------- next part --------------
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. 
::: Messages without supporting info will risk being sent to /dev/null