perfSONAR User Q&A and Other Discussion

[Phil Reese <>]

All,

I can't believe I'd be the first to notice this but here goes.

I mostly look at network speed issues between systems around campus and 
between campus and other U's.  To help with this, most all the systems I 
build, I add the perfsonar-tools Bundle, so I can test against the 
system in the future.

I'm struggling to get beyond the neural pathways of typing 'bwctl ...' 
for all my tests and trying to type 'pscheduler ...' for my tests.

I recently did a fresh install of Centos 7.3 and then the 
perfsonar-tools bundle install.  I casually did a 'pscheduler --help' 
just to confirm it was installed.  It was.  I of course then did a bunch 
of 'bwctl' tests and then stopped myself and said try the 'new' thing.   
I tried a pscheduler command line it failed with a particularly odd 
error message.  See below.  I've now tried this with two or three 
additional fresh install hosts, all giving the same 'Unable to find 
pScheduler' error.

Did some files get jumbled as the final bundles were put together? I can 
sure imagine that during development, that pScheduler was a test tool 
name, but it shouldn't be in the final version, should it?

Thoughts?
Phil

-----
[preese@srn-dy6 ~]$ pscheduler --help
Usage: pscheduler command [ arguments ]

Commands:  (Use 'command --help' for further help.)

-----
[preese@srn-dy6 ~]$ pscheduler task throughput --dest <local-host>
Unable to find pScheduler on localhost