On Wed, Jun 23, 2010 at 6:01 PM, Greg Fishback <[email protected]> wrote: > Yep, kind of what I expected. When I put > check_file_age=cscript.exe scripts\check_file_age.vbs -f > "c:\temp\test.txt" -w 1 -c 3 > in the NCS.ini file and then run ./check_nrpe -H hostname -c check_file_age > from the linux prompt I get the appropriate respons. In this case, > "WARNING".
ok, so it is working. Now the other details. > When I replace the NCS.ini entry with > check_file_age=cscript.exe scripts\check_file_age.vbs $ARG1$ > and then run > ./check_nrpe -H computername -c check_file_age -f "c:\temp\test.txt" -w 1 > -c 3 > It returns nothing. Just getting the "\" character involved me using the > extended ascii code and on my keyboard the @ and " (quote) files were > swapped. Obviously the argument string is not arriving correctly at the > client machine. I'm not sure it's related to that. The macros $ARG1$, $ARG2$, etc, are the arguments you pass check_nrpe, so you could try this: in nsc.ini, check_file_age=cscript.exe scripts\check_file_age -f $ARG1$ -w $ARG2$ -c $ARG3$ (then reload the service). In the linux promt: ./check_nrpe -c check_file_age "c:\temp\test.txt" 1 3 It should work (i think, untested, obviously, but ...). > Greg -- natxo _______________________________________________ Opsview-users mailing list [email protected] http://lists.opsview.org/lists/listinfo/opsview-users
