On 05/02/2013 01:13 PM, Mark Goodwin wrote:
... we could have checked sts == PM_ERR_IPC || sts == PM_ERR_TIMEOUT
in pmFetch and automatically reconnected/retried some number of
times. Or maybe that's too messy and we needed the error handling
out in the app layer? e.g. in the above case, pmstat would have seemed
to hang with no opportunity to inform the user whilst pmFetch reconnected
and retried. Can you remember Ken?
actually, I think I remember now - tools like pmchart and pmie
use multiple contexts, not necessarily all to the same host. So
if one of those host contexts bounces, they don't all have to
hang whilst it reconnects/retries (and we have no async fetch,
.. well we did, but not at the time pmReconnectContext came along,
and async libpcp functionality is gone now anyway!)
-- Mark
|