Nathan Scott

@jelly OOC, what is the reason for not using the python3-pcp package?

@myllynen the parser we're using is fairly relaxed in the JSON it accepts - its treating "foo" as a valid token here (a key named "foo" with no value). We...

@myllynen I take back my earlier "we're not likely to do that ourselves" comment - we've begun switching over to an alternate JSON parsing implementation, and I've confirmed the cases...

> And I still think that providing extra, special tracing libraries as part of rdma-core is wrong approach. I came here looking for tracing in rdma-core too, after recent involvement...

@kurik I think there's two cases here. Some directories are missing from our makefiles, fixing this should resolve the issue for those cases, e.g. ``` $ rpm -qf /etc/pcp/pmlogredact /usr/share/doc/pcp-doc...

@turbo fantastic! Could you open a PR? On very quick review, I notice some comments mentioning "Redis" - we support either Redis/Valkey now, and so code was changed to generically...

That script needs some love to modernize it. A few notes from scanning it: - it hard-codes /tmp use and uses predictable file names, better to use mktemp(1) (see pcp(1)...

In pcp.git have a look at scripts like build/mac/installer-resources/postinstall - creates the "pcp" user account, etc - the ruby packaging here will need to do similar things I imagine, not...

@tallpsmith I have PCP building and installing the dmg packages on El Capitan now (see master branch, git.pcp.io/pcp, via ./Makepkgs) - those latest changes should also go a long way...

@eberbesi thanks for the details! One possible option that might help you with this aspect (I recommend this whether your filename contains Slurm job details or not) ... > Ideally,...