демон сборщика показателей производительности (performance metrics collector daemon)
RECONFIGURING PMCD
If the configuration file has been changed or if an agent is not
responding because it has terminated or the PMNS has been
changed, pmcd may be reconfigured by sending it a SIGHUP, as in
# pmsignal -a -s HUP pmcd
When pmcd receives a SIGHUP, it checks the configuration file for
changes. If the file has been modified, it is reparsed and the
contents become the new configuration. If there are errors in
the configuration file, the existing configuration is retained
and the contents of the file are ignored. Errors are reported in
the pmcd log file.
It also checks the PMNS file and any labels files for changes.
If any of these files have been modified, then the PMNS and/or
context labels are reloaded. Use of tail(1) on the log file is
recommended while reconfiguring pmcd.
If the configuration for an agent has changed (any parameter
except the agent's label is different), the agent is restarted.
Agents whose configurations do not change are not restarted. Any
existing agents not present in the new configuration are
terminated. Any deceased agents are that are still listed are
restarted.
Sometimes it is necessary to restart an agent that is still
running, but malfunctioning. Simply stop the agent (e.g. using
SIGTERM from pmsignal(1)), then send pmcd a SIGHUP, which will
cause the agent to be restarted.
