TCP ping?

[Fabien SEISEN]

"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 :)

cf: 
docs/1_0/networkreachability.html
"If a host check command for a remote host returns a non-OK state,
Nagios will "walk" the depency tree (as shown in the figure above) until
it reaches the top (or until a parent host check results in an OK
state)."

-- 
Fabien Seisen 
http://pouxvert.linuxfr.org/
GnuPG ID 1024D/112189D8


-------------------------------------------------------
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