https://bugzilla.redhat.com/show_bug.cgi?id=1376856
--- Comment #6 from Frank Ch. Eigler <[email protected]> ---
> I don't think you followed completely.
On the contrary, I followed completely.
> So, the assertion this is a new regression is incorrect - the pmmgr
> assumption that pmcd would be restarted on PMDA install has always been
> incorrect.
Since more cases now trigger this "incorrect" assumption, it is obviously
both "new" and a "regression".
> However, this *is* fixable in pmmgr. If pmmgr maintains a connection to
> pmcd, it would be able to detect both PMDA reconfiguration messages and loss
> of connection to pmcd - and could act in the way you feel is desirable here.
Yes, that could work, assuming a cooperative libpcp.
It would not help those users stuck with service-pmlogger. I guess they are
to further fall behind in terms of responsiveness.
> [...]
> You continue to dismiss the situation where people write their own rules,
> rather than use pmieconf, but in practice for many pmie deployments this is
> the norm.
I don't dismiss it in the abstract. This case is simply not relevant to
pmmgr's normal host-targeted model. It is off topic. People with such
pmie rules can run them with service-pmie (or even with service-pmmgr,
linked to a dummy host). It is off topic.
--
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=f8uDyWT6Ah&a=cc_unsubscribe
_______________________________________________
pcp mailing list
[email protected]
http://oss.sgi.com/mailman/listinfo/pcp
lmpx.com only provides a reader for public news (NNTP) servers. It is not
affiliated with the servers or forums shown here and is not responsible for
the content of articles, which is written by their respective authors.