<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> <HTML> <HEAD> <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1"> <META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7232.36"> <TITLE>RE: [Nagios-users] Advice on Plugin Development</TITLE> </HEAD> <BODY>  If you write your event handler in Perl, then you can just use <A HREF="HTTP::Request">HTTP::Request</A> POST to handle the transaction that way, it's nice and clean. If you want to do it in shell you can pipe your http transactions through nc. /eli -----Original Message----- From: nagios-users-admin@lists.sourceforge.net on behalf of Nick Weisser Sent: Sat 12/17/2005 11:22 PM To: nagios-users@lists.sourceforge.net Subject: [Nagios-users] Advice on Plugin Development Hi there, I need a plugin for Nagios that reboots an external server under certain circumstances (no ping response). There is no "direct connection" between the machine that Nagios runs on and the monitored server, so the reboot needs to be initiated via HTTPS with several POST parameters, i.e. a "simple" web form. I've been using Nagios for quite some time now, but I'm not sure if this can be realized with a plugin or what other approaches are possible. Any comments would be greatly appreciated. -- Regards Nick ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! <A HREF="http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click">http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click</A> _______________________________________________ Nagios-users mailing list Nagios-users@lists.sourceforge.net <A HREF="https://lists.sourceforge.net/lists/listinfo/nagios-users">https://lists.sourceforge.net/lists/listinfo/nagios-users</A> ::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. ::: Messages without supporting info will risk being sent to /dev/null </BODY> </HTML>