Duncan Ferguson wrote: > Can you please try a recent snapshot? The I rewrote the pst3 binary to > enable to work faster and be zone aware (to allow use in in the global > and sub zones). Its been fine for me, but I don't think there has been > a release since the code was committed. > > CC'ing in the nagiosplug-devel list (probably best place for this thread).
Hmmm ... I took the 15 September snapshot at http://nagiosplug.sourceforge.net/snapshot/ [EMAIL PROTECTED] ~]$ /opt/adnnagios/libexec/check_procs-new -V check_procs v2019 (nagios-plugins 1.4.12) [EMAIL PROTECTED] ~]$ time /opt/adnnagios/libexec/check_procs-new -t 60 PROCS OK: 1445 processes real 0m32.551s user 0m1.641s sys 0m26.088s [EMAIL PROTECTED] ~]$ time /opt/adnnagios/libexec/check_procs-1.45 -t 60 PROCS OK: 1477 processes real 0m0.344s user 0m0.056s sys 0m0.309s Still runs about 100x slower than version 1.45. [EMAIL PROTECTED] ~]$ uname -a SunOS adnsoz05 5.10 Generic_127127-11 sun4u sparc SUNW,SPARC-Enterprise [EMAIL PROTECTED] ~]$ prtdiag System Configuration: Sun Microsystems sun4u Sun SPARC Enterprise M4000 Server System clock frequency: 1012 MHz Memory size: 32768 Megabytes ==================================== CPUs ==================================== CPU CPU Run L2$ CPU CPU LSB Chip ID MHz MB Impl. Mask --- ---- ---------------------------------------- ---- --- ----- ---- 00 0 0, 1, 2, 3 2150 5.0 6 147 00 1 8, 9, 10, 11 2150 5.0 6 147 ============================ Memory Configuration ============================ Memory Available Memory DIMM # of Mirror Interleave LSB Group Size Status Size DIMMs Mode Factor --- ------ ------------------ ------- ------ ----- ------- ---------- 00 A 16384MB okay 2048MB 8 no 4-way 00 B 16384MB okay 2048MB 8 no 4-way Bye Bernd > > Duncs > > On 4 Sep 2008, at 14:02, Bernd Nies wrote: > >> Hi, >> >> Something bad happened to the check_proc plugin between version 1.45 and >> v1991. For counting ca 1700 processes on a Sun Enterprise M4000 it takes >> 45 seconds and sometimes longer. An older version was much faster qirh >> 0.3 seconds. >> >> I compiled Nagios plugins 1.4.12 on a Solaris 9 with GCC 3.4.6 to get >> binaries that can run on Solaris 8, 9 and 10. >> >> >> >> [EMAIL PROTECTED] ~]$ /opt/adnnagios/libexec/check_procs-1.45 -V >> check_procs (nagios-plugins 1.4.1) 1.45 >> >> [EMAIL PROTECTED] ~]$ /opt/adnnagios/libexec/check_procs -V >> check_procs v1991 (nagios-plugins 1.4.12) >> >> >> >> [EMAIL PROTECTED] ~]$ time /opt/adnnagios/libexec/check_procs-1.45 >> PROCS OK: 1695 processes >> >> real 0m0.320s >> user 0m0.051s >> sys 0m0.296s >> >> [EMAIL PROTECTED] ~]$ time /opt/adnnagios/libexec/check_procs -t 60 >> PROCS OK: 1664 processes >> >> real 0m45.543s >> user 0m2.851s >> sys 0m41.231s >> >> >> Any ideas what's going wrong? >> >> Bye >> Bernd >> >> >> ------------------------------------------------------------------------- >> This SF.Net email is sponsored by the Moblin Your Move Developer's >> challenge >> Build the coolest Linux based applications with Moblin SDK & win great >> prizes >> Grand prize is a trip for two to an Open Source event anywhere in the >> world >> http://moblin-contest.org/redirect.php?banner_id=100&url=/ >> _______________________________________________ >> 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 > ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ 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
