Hi folks,

Just came across this bug, apologies, I would have provided input earlier.

Regarding using pcp-dstat as drop-in replacement for dstat, this is a
transition that Fedora and RHEL made several years ago without issues
(FWLIW).  Dstat development continued within PCP, with support for GPU
reporting and various other bits and pieces in recent times.

Regarding the concerns that PCP installs daemons for remote system
monitoring and recording system activity - these should not have been
auto-started, that sounds like a bug (perhaps fixed by now? not sure)
and the default networking mode should be localhost access only, as it
is on Fedora and RHEL.

There is no requirement to have these daemons running to use the PCP
dstat script - it will automatically use the PCP "local context"
(shared library) mode of operation if pmcd is not running.

For anyone doing system performance analysis with dstat, IMO the
biggest improvement PCP support introduced to the new dstat script is
the ability to perform retrospective analysis using recorded PCP
archives.

Feel free to contact me ([email protected] | [email protected]) if
any further info is needed.

cheers.

-- 
Nathan

Reply via email to