* Ken McDonell wrote:
> pmie with the -v option is much more general, and has less formatting
> fluff around the output. I have appended some old mail on this subject
> and the pmie2col script is attached.
Yes, I discovered that pmie would do this yesterday!
> Patches that are backwards compatible, consistent with PCP the command
> line options rules, and add value are always of interest ... send 'em
> on down.
OK, I'll send them.
> I think this is a deeper issue ... many of the PMDAs won't work at all
> without a half-sane configuration. Many of the PMDAs already work with
> non-interactive or /dev/null input.
> In the case of the weblog PMDA ... there is a script that is supposed
> to find the activity logs for a variety of web servers
> (/var/pcp/pmdas/weblog/server.sh) if this cannot find your web server
> activity logs, then (a) fix the script and send the patches in, else
> (b) use the environment variables of the form $FOOPATH in the script to
> guide the search for your activity logs.
The problem is that this imposes all sorts of horrible dependencies on
installation order &c. For instance we have machine installations
where it's not clear at the point when things like PCP are installed
where the web server logs will go, because we don't (yet) know what
kind of web (or other) server it will run, as its essentially a
cold-standby machine. We could reorder everything to install PCP much
later, but that's painful for various other reasons (for instance we
can't test that PCP is installed until it is, so that would have to be
after the web server is set up, which is time-critical). I just want
to be able to tell it `it's OK, I will make sure you have a correct
config file when the time comes', without having to work out
everything the script does myself...
--tim
|