NSCP

More vagrant wrapper script fixes (might actually work now)

converted to unix format

added initial vagrant builder script

Fixed some build issues

Fixed issue in check_drivesize and some drive types Improved error reporting from check_drivsize Improved speed in fetching drives a tad

Implemented insecure option to nrpe client

(re)Added NRPE multi packet patch Fixed NRPE client to work with certificates Changed certificate length (auto generated) to 2048 bits

removed NRPE dependencioes from webserver

Hi, I use last NSClient version 0.4.2. I use 'total_free' for threshold (avoid false postiive on big disks). /usr/lib64/nagios/plugins/check_nrpe -H xxx.xxx.xxx.xxx -p 5666 -c check_drivesize -a "drive=*" "perf-config=free(unit:B)free ... [More] %(ignored:true)" "filter=type = 'fixed' and name not regexp '.*syst.*'" "warning=total_free<5G" "critical=total_free<2G" OK |'C:\ free'=102535319552B;5368709120;2147483648;0;135996108800 Perfdata are ok but i would like to have 'used' (not 'free' perfdata). There is an option for that ? [Less]

I have upgraded nsclient 0.3.9-x64 to 0.4.1.102-x64 on several machines and I'm seeing higher CPU usage through Nagios XI. I'm using Nagios XI 2014R1.1 and the check_nt that comes with it and the following command :check_nt -H MyIP -s MyPassword? -p ... [More] MyPort? -v CPULOAD -l 5,95,97 CPU usage on all systems was +/- 2% when I performed this test with NSclient 0.3.9 installed. Since the upgrade to Nscp 0.4.1.102 the test returns +/- 17% on all (quad core) systems although I still see an average of +/2% on the systems if I look at it. When I check the CPU usage with perfmon on these machines I still see +/-2% usage ? Is there a logical explanation for this or is this a bug ? [Less]