| To: | pcp <pcp@xxxxxxxxxxx> |
|---|---|
| Subject: | pmcc.py bug? |
| From: | Mark Goodwin <mgoodwin@xxxxxxxxxx> |
| Date: | Thu, 29 May 2014 17:47:19 +1000 |
| Delivered-to: | pcp@xxxxxxxxxxx |
| User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0 |
pmcc doesn't seem to update it's metric values after each fetch beyond the first, but I may be calling it incorrectly. Here's a simple program demonstrating the issue, and a simple patch to pmcc.py that fixes it (but introduces a memory leak?). So is this a bug or am I not using pmcc correctly? Thanks for any help ... Mark.
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [pcp] python pmExtractValue segfault, Nathan Scott |
|---|---|
| Next by Date: | Re: Service advertising versus QA, Dave Brolley |
| Previous by Thread: | Re: [pcp] Dropping machines from my QA farm, Josef 'Jeff' Sipek |
| Next by Thread: | Re: [pcp] pmcc.py bug?, Nathan Scott |
| Indexes: | [Date] [Thread] [Top] [All Lists] |