I am just wondering if the RUNSCRIPT command can accept a variable to be passed to the client?
so this is my sample command I ran
# ./check_nt -H borl01 -v RUNSCRIPT -l test-echo.bat
so that test-echo.bat just echo's back whatever variable is passed to it.
Yes it can.
You need to set the options in the startup.cfg in order to allow this. these options were added to the startup to increase the security of RUNSCRIPTS
allow_run_scripts true Enables accepting the RUNSCRIPT command
script_timeout 30 Is the time in seconds that is alloted for the script to run, if the script does not finish then it is killed.
do_not_blaim_nc_net true enables the entire command line to be sent to RUNSCRIPT.
RUNSCRIPT is then going to return the return code of the script and the output of the command.
TOny
thanx! that was what i was looking for. sorry must have missed it in the docs
It was only documented in the Startup.cfg and maybe in the check_nt --help=RUNSCRIPT
Good luck Tony
Log in to post a comment.
I am just wondering if the RUNSCRIPT command can accept a variable to be passed to the client?
so this is my sample command I ran
# ./check_nt -H borl01 -v RUNSCRIPT -l test-echo.bat
so that test-echo.bat just echo's back whatever variable is passed to it.
Yes it can.
You need to set the options in the startup.cfg in order to allow this.
these options were added to the startup to increase the security of RUNSCRIPTS
allow_run_scripts true
Enables accepting the RUNSCRIPT command
script_timeout 30
Is the time in seconds that is alloted for the script to run, if the script does not finish then it is killed.
do_not_blaim_nc_net true
enables the entire command line to be sent to RUNSCRIPT.
RUNSCRIPT is then going to return the return code of the script and the output of the command.
TOny
thanx! that was what i was looking for. sorry must have missed it in the docs
It was only documented in the Startup.cfg and maybe in the check_nt --help=RUNSCRIPT
Good luck
Tony