> -----Original Message----- > From: [EMAIL PROTECTED] [mailto:nagios-users- > [EMAIL PROTECTED] On Behalf Of Scott Sanders > Sent: Wednesday, January 23, 2008 8:39 AM > To: [email protected] > Subject: Re: [Nagios-users] Determining the success or failure of > externalcommands >
> nagios.cmd pipe. In order for the external command functionality to work > the way I intend, I need to obtain a response from nagios so my server can > respond back to the client with the results of processing the external > command. I am really hoping there is an easy way to do this, as replacing > the nagios.cmd file with something besides a FIFO pipe requires > modification to the nagios source and is something I was trying to avoid. Nagios was never designed to provide status back to a script submitting a command to the external command pipe because it is not a real-time operation and the commands should always succeed (why wouldn't they?). The command may not be read for quite some time after it's submitted, depending on what nagios is doing at the time. As for logging, Nagios assumes that all external commands succeed and logs nothing unless the command is malformed. There is additional logging that is available by running nagios in DEBUG3 but that still doesn't indicate success or failure. commands.c handles external commands. I'd suggest you start there and add in what additional logging you feel you need. -- Marc ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Nagios-users mailing list [email protected] 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
