pmie hostname handling bugs (was Re: [pcp] pmlc access control, was [something else again])

[Nathan Scott <nathans@xxxxxxxxxx>]

----- Original Message -----
> 
> > The usual model would be local pmie daemon (no temporary connection).
> 
> Sorry, I was extrapolating from observations of a particular local
> pmie process here, which maintained no permanent tcp connection to the
> -h HOSTNAME, but rather closed / reopened it every pmie polling cycle.
> But looking at it now more closely, the affected pmie is one that is
> using an ssh tunnel (-h localhost:XYZ), where the remote pmcd.hostname
> is of course different from localhost etc.  I see pmie trying to
> connect to the pmcd.hostname, failing (since it's firewalled that
> route), then falling back to the initially supplied -h HOSTSTRING.
> There's a real bug in there.
> 

*nod* - the hostname mismanagement we observed with local: handling in
pmie is also in that neck of the woods (a separate copy of the hostname
is kept in internal data structures, and used for newContext calls - it
seems to lack the differentiation between "connection string" and "host
name" that's been introduced everywhere else).

My bug list is already long, if someone else could take these on that'd
be fantastic.  Hopefully its just the one underlying issue.

cheers.

--
Nathan