| To: | performancecopilot/pcp <pcp@xxxxxxxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: [pcp] pminfo -t aborts pmcd (#30) |
| From: | Ken McDonell <notifications@xxxxxxxxxx> |
| Date: | Tue, 30 Jun 2015 13:45:27 -0700 |
| Delivered-to: | pcp@xxxxxxxxxxx |
| Dkim-signature: | v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1435697127; bh=A8AU9e9ZRQCZb4fFMQ68YkS1O6TgmnpzuCEgnIEBqVY=; h=From:Reply-To:To:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=kuy04D3tzoFHfBnbGNQ9CRH51W+UJ4YAT0lys2nHyTLvhYDUBzPASIJTzWiFfG4cL t7G3GUcDAFzVcWgio8fLL8yOhj1upck8OtI9xeaMz1OvFlb+kSHxrFjLUrfJL6L5bn QStKT1VVjRuR2Q/IRx+r7QE2wYTKJVxrhnb0ML1k= |
| In-reply-to: | <performancecopilot/pcp/issues/30@xxxxxxxxxx> |
| List-archive: | https://github.com/performancecopilot/pcp |
| List-id: | performancecopilot/pcp <pcp.performancecopilot.github.com> |
| List-post: | <mailto:reply+00bd08b66117bcce398573b5b927abfbaa20b7da610425dc92cf0000000111aac1e792a169ce057c1750@reply.github.com> |
| List-unsubscribe: | <mailto:unsub+00bd08b66117bcce398573b5b927abfbaa20b7da610425dc92cf0000000111aac1e792a169ce057c1750@reply.github.com>, <https://github.com/notifications/unsubscribe/AL0ItgYv8_XG6AYyAo1ZdQx4mfn0H-Czks5oYvdngaJpZM4FOwu4> |
| References: | <performancecopilot/pcp/issues/30@xxxxxxxxxx> |
| Reply-to: | performancecopilot/pcp <reply+00bd08b66117bcce398573b5b927abfbaa20b7da610425dc92cf0000000111aac1e792a169ce057c1750@xxxxxxxxxxxxxxxx> |
|
Some of the code is not 20 years old ... but you're right, this should not happen, even for PCP 3.8.12 which is 22 releases in the past and was released 18 months ago. It is certainly not reproducible on my local Ubuntu system with the latest PCP version. There is already a test in the QA suite for 'pminfo -t' followed by 'pminfo -T' and I cannot recall this test ever failing in the way you describe (and it is run many times on dozens of machines, including Ubuntu, during any release cycle ... and would have been run prior to the 3.8.12 PCP release). So this is probably not a generic issue, but something specific to your setup. Are you able to upgrade to a newer version from the PCP project web site or bintray.com? If not, or if the problem persists, the following additional information would help us diagnose the root cause:
— |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | [pcp] pminfo -t aborts pmcd (#30), ABC |
|---|---|
| Next by Date: | Re: [pcp] pminfo -t aborts pmcd (#30), Frank Ch. Eigler |
| Previous by Thread: | [pcp] pminfo -t aborts pmcd (#30), ABC |
| Next by Thread: | Re: [pcp] pminfo -t aborts pmcd (#30), Frank Ch. Eigler |
| Indexes: | [Date] [Thread] [Top] [All Lists] |