| To: | pcp@xxxxxxxxxxx |
|---|---|
| Subject: | [Bug 1144] New: when pmcd gives up on a pmda, it should explain what it was doing |
| From: | bugzilla-daemon@xxxxxxxxxxx |
| Date: | Mon, 06 Jun 2016 20:16:47 +0000 |
| Auto-submitted: | auto-generated |
| Delivered-to: | pcp@xxxxxxxxxxx |
When there is a pmcd<->pmda communication breakdown (timeout or whatever), the pmcd logs are quite opaque as to -why-. It should log the last request to the pmda (a fetch? initial handshaking? ...?) and any other such nearby info that can help a pcp developer diagnose what went wrong. Similarly, a pmda that encounters an EOF from pmcd should log its recent history, like the type of packet it was just trying to respond to. You are receiving this mail because:
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | çå: [pcp] [patch] Add a new command pcp-ipcs, Wu, Liming |
|---|---|
| Next by Date: | ÐÐÐÐÑÐ ÐÐÐÐÐÐÐÐÑ Ð ÑÐÐÑÐÐÑÐÐÐÐÐÐ ÐÐÑÐÐÐÑÐÐÐÐÐÐÐÐ., ÐÐÐÐÐ Ð ÐÐÑÐÐÐÑÐÐÐÐÐÐÐÐ |
| Previous by Thread: | pcp updates: pcp-ipcs, build, docs, qa, Nathan Scott |
| Next by Thread: | ÐÐÐÐÑÐ ÐÐÐÐÐÐÐÐÑ Ð ÑÐÐÑÐÐÑÐÐÐÐÐÐ ÐÐÑÐÐÐÑÐÐÐÐÐÐÐÐ., ÐÐÐÐÐ Ð ÐÐÑÐÐÐÑÐÐÐÐÐÐÐÐ |
| Indexes: | [Date] [Thread] [Top] [All Lists] |