RE: [Ganglia-developers] 2.6.0 -Solaris kstat cpu_info

2004-04-06 Thread Adesanya, Adeyemi
CTED] > Subject: Re: [Ganglia-developers] 2.6.0 -Solaris kstat cpu_info > > > Martin, > > Here's the "diff -u " output of the original solaris.c and my > updated solaris.c. This is an odd scenario, but it could > come up in certain environments (l

Re: [Ganglia-developers] 2.6.0 -Solaris kstat cpu_info

2004-04-03 Thread Michael Hom
IL PROTECTED]To: Michael Hom/NewYork/DBNA/[EMAIL PROTECTED] de> cc: [EMAIL PROTECTED], ganglia-developers@lists.s

Re: [Ganglia-developers] 2.6.0 -Solaris kstat cpu_info

2004-04-02 Thread Martin Knoblauch
Michael, could you please post a "diff -u" style patch, so that I can apply it automatically (alternatively just send me your version of solaris.c). Robert: could you have a look at the change for sanity/correctness? Apparently your previous fix did not take into account the case that CPU #0 is

[Ganglia-developers] 2.6.0 -Solaris kstat cpu_info

2004-04-02 Thread Michael Hom
OS: Solaris 5.8, 5.9 File: "tarball/gmond/machines/solaris.c" Function: get_kstat_val( ) I've been testing the latest ganglia 2.6.0 posted on March 22nd. I noticed that gmond segfaults & core dumps when the first online cpu is NOT in slot #0. When I do a "kstat cpu_stat", my cpus are instance #