| To: | pcp@xxxxxxxxxxx |
|---|---|
| Subject: | Re: [pcp] Multi-archive Contexts: Some PCP Tools Lost in Time |
| From: | Ken McDonell <kenj@xxxxxxxxxxxxxxxx> |
| Date: | Wed, 17 Feb 2016 08:33:35 +1100 |
| Delivered-to: | pcp@xxxxxxxxxxx |
| In-reply-to: | <20160216194348.GC2398@xxxxxxxxxx> |
| References: | <56C3608E.9090404@xxxxxxxxxx> <y0mvb5oa323.fsf@xxxxxxxx> <56C37828.10007@xxxxxxxxxx> <20160216194348.GC2398@xxxxxxxxxx> |
| User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.5.1 |
Whoa ... hold on ... I think all of - pmlogdump - pmlogcheck - pmlogrewrite should / could be constrained to operate on a single archive at a time.They are all "special" tools for munging with _an_ archive, and as such could be embargoed from the "operate on a directory of archives" rules of engagement. By design (and of need) they probe around and below the PMAPI. Would that make life easier? |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | pmrep: adjust exit codes, Marko Myllynen |
|---|---|
| Next by Date: | Re: [pcp] pmrep error on RHEL6.4 / python2.66, Nathan Scott |
| Previous by Thread: | Re: Multi-archive Contexts: Some PCP Tools Lost in Time, Frank Ch. Eigler |
| Next by Thread: | Re: Multi-archive Contexts: Some PCP Tools Lost in Time, Frank Ch. Eigler |
| Indexes: | [Date] [Thread] [Top] [All Lists] |