| To: | "Frank Ch. Eigler" <fche@xxxxxxxxxx>, Lukas Berk <lberk@xxxxxxxxxx> |
|---|---|
| Subject: | Re: pcp updates - pmdapapi update |
| From: | Nathan Scott <nathans@xxxxxxxxxx> |
| Date: | Mon, 17 Nov 2014 17:30:49 -0500 (EST) |
| Cc: | pcp@xxxxxxxxxxx |
| Delivered-to: | pcp@xxxxxxxxxxx |
| In-reply-to: | <y0mppclczva.fsf@xxxxxxxx> |
| References: | <87oascow3f.fsf@xxxxxxxxxx> <50063157.14443613.1415955185726.JavaMail.zimbra@xxxxxxxxxx> <y0mppclczva.fsf@xxxxxxxx> |
| Reply-to: | Nathan Scott <nathans@xxxxxxxxxx> |
| Thread-index: | +eMGV1yLgsESHbOZkadLV2/pqbRliA== |
| Thread-topic: | pcp updates - pmdapapi update |
----- Original Message ----- > > [...] - As per earlier mail, there's no error handling for auto-fu > > counters. [...] > > Does this cover the case? There's two parts to this problem. The first part is that patch (for auto-enabling), the second part is during disabling - where do those errors go? At the moment, they are all silently discarded. I think they at least need to be logged in papi.log - that's the best we can do, I guess? - there's no way to tell the client, which may not even be running anymore. Also, once we have logging of errors on auto-disable, we should add checks to the existing tests to scan for errors in papi.log (just a "cat" on the papi.log file should do the trick, with some date/time filtering for the PMDA start/stop messages that are always logged). cheers. -- Nathan |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: pcp updates - pmdapapi update, Frank Ch. Eigler |
|---|---|
| Next by Date: | Re: [pcp] [RFC] pcp python patch, Nathan Scott |
| Previous by Thread: | Re: pcp updates - pmdapapi update, Frank Ch. Eigler |
| Next by Thread: | Re: pcp updates - pmdapapi update, Frank Ch. Eigler |
| Indexes: | [Date] [Thread] [Top] [All Lists] |