On Feb 15, 2008 5:42 PM, Bernard Li <[EMAIL PROTECTED]> wrote: > Sure, please update us after the weekend, we'll likely release 3.0.7 then.
Running valgrind on the ganglia-3.0.6.200802141157.tar.gz tarball you posted for testing: ==2590== 5,554 bytes in 1,282 blocks are definitely lost in loss record 13 of 16 ==2590== at 0x4904A06: malloc (vg_replace_malloc.c:149) ==2590== by 0x3DCEC707E1: strndup (in /lib64/tls/libc-2.3.4.so) ==2590== by 0x407F74: bytes_out_func (in /usr/sbin/gmond) ==2590== by 0x404A54: Ganglia_collection_group_collect (in /usr/sbin/gmond) ==2590== by 0x404CB0: process_collection_groups (in /usr/sbin/gmond) ==2590== by 0x405190: main (in /usr/sbin/gmond) ==2590== ==2590== LEAK SUMMARY: ==2590== definitely lost: 5,554 bytes in 1,282 blocks. ==2590== possibly lost: 0 bytes in 0 blocks. ==2590== still reachable: 415,977 bytes in 998 blocks. ==2590== suppressed: 0 bytes in 0 blocks. I modified my gmond.conf to report much more aggressively than usual so that the test time would be shorter. However, with *this configuration*, it works out to about 770 bytes per minute. -- Jesse Becker GPG Fingerprint -- BD00 7AA4 4483 AFCC 82D0 2720 0083 0931 9A2B 06A2 ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Ganglia-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ganglia-developers
