Feature request: Disabling pmlogger_janitor and pmlogger_farm service

[orasagar]

In our current development, we run a single pmlogger instance per server. To streamline server provisioning and maintenance, we require a configuration-based method to disable the pmlogger_janitor and pmlogger_farm services by default, rather than manually disabling them on each new server. Ideally, this should be implemented as an optional setting, allowing users to choose whether or not to enable these services according to their operational requirements.

[kmcdonell]

@orasagar I need a bit more context here. By design ...

• pmlogger_farm is a NOOP service unless there are non-primary loggers configured in or below /etc/pcp/pmlogger/control*.
• pmlogger_janitor is a NOOP script unless the pmlogger configuration is changed and there are corpses left lying around.

You should not need any manual intervention to disable either.

If you're seeing bad side-effects from these services and/or scripts, please share those details ... it is more likely that we need to fix the scripts than provide a lever to disable the associated services (and pmlogger_janitor is not a service it is a script run from pmlogger_check so it is associated with both the pmlogger and pmlogger_farm services).