| To: | pcp@xxxxxxxxxxx |
|---|---|
| Subject: | [Bug 1158] pmcd observed to return PMNS_IDS PDU in response to FETCH |
| From: | bugzilla-daemon@xxxxxxxxxxx |
| Date: | Fri, 29 Jul 2016 00:18:41 +0000 |
| Auto-submitted: | auto-generated |
| Delivered-to: | pcp@xxxxxxxxxxx |
| In-reply-to: | <bug-1158-835@xxxxxxxxxxxxxxxx/bugzilla/> |
| References: | <bug-1158-835@xxxxxxxxxxxxxxxx/bugzilla/> |
|
Comment # 8
on bug 1158
from Frank Ch. Eigler
I believe we tried setting $PCP_DEBUG in order to help diagnose indicated IPC failures that may or may not have been timeouts. How are timeouts on the libpcp<->pmcd channel supposed to work? In theory, a timeout should close the connection? But if the lower level socket is shared between contexts, then this closing does not occur and things get farther out of whack? You are receiving this mail because:
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | [Bug 1158] pmcd observed to return PMNS_IDS PDU in response to FETCH, bugzilla-daemon |
|---|---|
| Next by Date: | [Bug 1158] pmcd observed to return PMNS_IDS PDU in response to FETCH, bugzilla-daemon |
| Previous by Thread: | [Bug 1158] pmcd observed to return PMNS_IDS PDU in response to FETCH, bugzilla-daemon |
| Next by Thread: | [Bug 1158] pmcd observed to return PMNS_IDS PDU in response to FETCH, bugzilla-daemon |
| Indexes: | [Date] [Thread] [Top] [All Lists] |