[Nagiosplug-help] How do i compile check_tracroute.pl?

[Nikolaos Loutzakis]

i found the utils.pm in the libexec folder. and i put with
check_traceroute.and when i want to define the command i put in the command
line command_line    check_traceroute -r -H  www.google.com for example??

and one more question. i want to make a plugin C based like those the
nagios-plugins-1.4.13 has. because i want to use same procedures and same
things you are using. but i have problem withe the configure and tha make
commands. i dont know what i have to change to makefile for example. can you
help me here? or to do it in another way. because i think the main idea of my
plugin will be like yours.

many thanks for helping me


Jon Angliss <jon at netdork.net> said:

> On Sat, 9 May 2009 12:08:14 -0000, "Nikolaos Loutzakis"
> <el04748 at mail.ntua.gr> wrote:
> 
> >
> >i want to ask how do i compile the files that are in the contrib folder like
> >check_traceroute.pl.i do the procedure you say so but it doesnt copile them
> 
> With an extension like .pl, it'd hint it is a perl script, and not a
> compilable script.  Meaning you should be able to execute as is.
> 
>   ./check_traceroute.pl --help
> 
> Make sure you have utils.pm in the path, or copy the file to the same
> location the other plugins are located.
> 
> -- 
> Jonathan Angliss
> <jon at netdork.net>
> 
> 
> ------------------------------------------------------------------------------
> The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
> production scanning environment may not be a perfect world - but thanks to
> Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
> Series Scanner you'll get full speed at 300 dpi even with all image 
> processing features enabled. http://p.sf.net/sfu/kodak-com
> _______________________________________________
> Nagiosplug-help mailing list
> Nagiosplug-help at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/nagiosplug-help
> ::: Please include plugins version (-v) and OS when reporting any issue. 
> ::: Messages without supporting info will risk being sent to /dev/null
> 



--