I'm afraid not.
That was outside the original scope.
And in fact pmie has accumulated so much state about metric meta data
and historical metric values, that any re-reading of the config file
would almost certainly mean forgetting all of that and starting again.
Functionally this would be like killing pmie and starting again ...
which is already supported .. 8^)>
Can you describe the scenario in which this might be useful? pmie is
already pretty robust in the face of changes in the underlying source of
metrics.
On Thu, 2008-05-08 at 13:15 -0400, Martin Hicks wrote:
> Hi,
>
> (switched from sending from my sgi account because they seem to like to
> strip off the "oss" from the domain...)
>
> Is there any way to force a running PMIE process to reread its config
> file? I had hoped that SIGHUP would do this, but it doesn't seem to.
>
> mh
>
|