Event Handler Arguments?

[Ethan Galstad]

Command arguments for event handlers, notifications, host checks, and 
other commands have already been implemented in the 2.x code. :-)

On 4 Jun 2003 at 17:34, Russell Scibetti wrote:

> I have a possibly useful feature request for Nagios.  Currently, in a
> service definition, the check_command line takes the name of a defined
> command, and then arguments (separated by "!").  These can then be
> references in the command as $ARG#$.
> 
> Now, the event_handler line also takes the name of a defined command,
> but there is no ability to pass arguments.  If the functionality
> already exists to pass arguments to a check_command, I can't see it
> being very difficult to implement for event_handlers as well.  Take,
> for example, a service that has a specific port pass to the
> check_command as an argument.  If you want to restart this service,
> you might need that port number again in the event handler.
> 
> So what do people think?  Ethan, would this be difficult to add for
> 2.0?  
> 
> Russell Scibetti
> Quadrix Solutions
> 
> -- 
> Russell Scibetti
> Quadrix Solutions, Inc.
> http://www.quadrix.com
> (732) 235-2335, ext. 7038
> 
> 
> 
> 
> -------------------------------------------------------
> This SF.net email is sponsored by:  Etnus, makers of TotalView, The
> best thread debugger on the planet. Designed with thread debugging
> features you've never dreamed of, try TotalView 6 free at
> www.etnus.com. _______________________________________________
> Nagios-devel mailing list Nagios-devel at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/nagios-devel
> 



Ethan Galstad,
Nagios Developer
---
Email: nagios at nagios.org
Website: http://www.nagios.org



-------------------------------------------------------
This SF.net email is sponsored by:  Etnus, makers of TotalView, The best
thread debugger on the planet. Designed with thread debugging features
you've never dreamed of, try TotalView 6 free at www.etnus.com.