Hi Martins,
----- Original Message -----
Hello,
Sorry to bring up an old thread, but we just ran into this issue
when upgrading from 3.8.0 to 3.8.6. We have an isolated cluster that we
are not worried about restricting access to proc metrics. We currently
do remote logging that includes the proc pmda. Was a backdoor way of
doing this implemented? If not, what is the suggested configuration to
make collecting all proc metrics work again from a remote host?
No backdoor was added, but I think for secure/test environments like your
case we perhaps should not make this quite so difficult. I've added in a
(-A, non-default) pmdaproc option to allow the checking to be switched off.
The alternative is a SASL2 setup for remote authentication, details here:
http://oss.sgi.com/projects/pcp/pcp-gui.git/man/html/lab.auth.html
cheers.
--
Nathan