If you installed the plugins from a source , one of the stages was "make install" That stage (usually the last one) places the plugins in the target directory ( if you did not change anything during the "configure" state , it will be in /usr/local/nagios/libexec )
So the steps are easy , IF you used source , go to the directory where the source package was extracted to , and in the directory type "make install" - that's it . however if you installed from RPM , then you'll need to reinstall the nagios-plugins rpm ( see the yjm /rpm man pages for that . dOE wrote: > Assaf, > > Could you explain with a little more detail how I could recover the > "check_tcp" from the source exactly? > > thanks > > On Tue, Jul 12, 2011 at 10:21 AM, Assaf Flatto <[email protected] > <mailto:[email protected]>> wrote: > > dOE wrote: > > Hi, > > > > I inadvertently deleted/overwrote the "check_tcp" file in > ../libexec. > > I tried copying the file back from another Nagios instance (same > build > > 3.0.3), but when I execute it it I get a "No such file or > directory". > > My permissions for the file are no different than other "checks_" in > > the directory. Is there something else I need to do other than > copy a > > file from another Nagios instance? > > > > > > rwxrwxr-x 1 nagios root 76K 2011-07-01 13:47 check_tcp > > > > > > Thanks > > > ------------------------------------------------------------------------ > ------------------------------------------------------------------------------ All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2d-c2 _______________________________________________ Nagios-users mailing list [email protected] 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
