| To: | pcp@xxxxxxxxxxx |
|---|---|
| Subject: | [Bug 1100] libpcp interp.c crash on archive scan |
| From: | bugzilla-daemon@xxxxxxxxxxx |
| Date: | Fri, 17 Jun 2016 18:19:18 +0000 |
| Auto-submitted: | auto-generated |
| Delivered-to: | pcp@xxxxxxxxxxx |
| In-reply-to: | <bug-1100-835@xxxxxxxxxxxxxxxx/bugzilla/> |
| References: | <bug-1100-835@xxxxxxxxxxxxxxxx/bugzilla/> |
|
Comment # 9
on bug 1100
from Frank Ch. Eigler
(In reply to comment #7) > (In reply to comment #6) > > The simplest response of exiting pmlogger upon > > a PMCD_ADD_AGENT could be fine. > > We'd rather not do this. In the most common case PMCD_ADD_AGENT happens > because a new (to pmlogger) PMDA has been added ... there is no reason to > terminate pmlogger if this happens. FWIW, one reason to terminate pmlogger is so that the monitoring system can analyze the new pmcd state - with a pmlogconf. That way, any conditional logging directives for the new pmda can be activated right away. You are receiving this mail because:
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: pcp updates: fche pmmgr/pmweb/qa, Frank Ch. Eigler |
|---|---|
| Next by Date: | [performancecopilot/pcp] Document default pmwebd context timeout (#96), Scott Emmons |
| Previous by Thread: | [Bug 1337212] derived metrics between singleton and indom' d metrics result in bad result indom, bugzilla |
| Next by Thread: | [Bug 1100] libpcp interp.c crash on archive scan, bugzilla-daemon |
| Indexes: | [Date] [Thread] [Top] [All Lists] |