Ken McDonell <kenj@xxxxxxxxxxxxxxxx> writes:
> [...] Upon further investigation it appears that my initial
> analysis was not quite correct, although the end result of a
> radically changed pmlogger configuration remains the same. [...]
> Rather than clobbering my config.foo as I had assumed,
> pmlogger_check has installed a new config.foo that pmlogger uses in
> lieu of my customized one. [...]
While the details of this problem were certainly unforseen, it lends a
little more weight to the idea of not intermingling hand-made and
generated files.
How about a solution of complete segregation? IOW, let's keep the
main pmlogger/pmie rc.d services for hand-made configurations as per
the status quo ante.
Instead, the new fully-automated configurations would be associated
only with the omninymous pcp-server-monitor widget I'll be prototyping
shortly, of which "local://" would be one default target (along with
avahi-*). The pcp-server-monitor service would be the one that causes
pure-default-pmlogconf of localhost (and optionally avahi-announced
and named remote nodes).
- FChE
|