Re: JSON PMDA

[Nathan Scott <nathans@xxxxxxxxxx>]

----- Original Message -----
> > [...]
> > That sounds good, except in the case where when the JSON PMDA was
> > started there were 3 JSON sources, and during the run a 4th was added.
> > Now the JSON PMDA gets restarted
> 
> ...  but according to normal practice, a "restarted pmda" means
> "restarted pmcd", which means active pcp contexts are dropped, which
> means clients are to reconnect & recalculate name->pmid mappings.

Some more context :- historically (and still now for many PMDAs) a SIGHUP
to pmcd was the default agent-restart/pmcd-reconfigure mechanism & that'll
become the default again soon for all PMDAs (so, no loss of connection for
clients).  The current situation requiring a pmcd restart was a compromise
(aka a bug :|) that was introduced with the unprivileged-pmcd changes, and
which will be fixed.

Is there any reason not to tackle this problem, Frank?  There's a possible
solution proposed reusing existing code, & other PMDAs that will benefit -
seems like a no-brainer that we should Just Do It.

cheers.

--
Nathan