TCP ping?

[Marc Powell]

> -----Original Message-----
> From: Fabien SEISEN [mailto:dakol at freesurf.fr]
> Sent: Thursday, December 04, 2003 12:11 PM
> To: nagios-users at lists.sourceforge.net
> Subject: Re: [Nagios-users] TCP ping?
> 
> "Marc Powell" <marc at ena.com> writes:
> 
> > A more flexible way of doing this so you don't have to create custom
> > check commands for every port would look like --
> >
> > define command {
> > 	command name check-tcp
> > 	command_line $USER1$/check_tcp -H $HOSTADDRESS$ -p $ARG1$
> > 	}
> >
> > define host {
> > 	host_name foo
> > 	yada yada
> > 	yada yada
> > 	address 127.0.0.1
> > 	}
> >
> > define service {
> > 	host_name foo
> > 	yada yada
> > 	yada yada
> > 	check_command check_tcp!15004
> > 	}
> 
> sure but, in "host state information", you will have
> "host assumed to be up" and hosts dependencies won't work.
> 
> It would be more flexible/convenient to be allowed to add arguments
> to check_command in a "define host { }"
> It is only possible on "define service {}"
> 
> i should write a patch :)
> 

AH, gotcha. I can be slow sometimes. Good news is you don't have to
write a patch. Already completed for nagios-2.0 --

	6. Host check commands, notification commands and event handler
command now accept arguments (using $ARGx$ macros)

--
Marc


-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive?  Does it
help you create better code?  SHARE THE LOVE, and help us help
YOU!  Click Here: http://sourceforge.net/donate/
_______________________________________________
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