[torqueusers] qtop: yet another tool to struggle with torque and PBS family systems
jbernstein at penguincomputing.com
Fri Sep 3 12:49:40 MDT 2010
I like the tool, but find its output a bit hard to read sometimes. The
biggest issue I have right now is that I can't seem to get color to
work, reguardless of what I do.
I've tried COLOR=1 ./qtop, FORCECOLOR=1 ./qtop, and I even have the
qtop.colormap installed in ~/.qtop. Anything else I'm missing?
Fotis Georgatos wrote:
> it is not uncommon for shepherds of PBS-family based clusters to wander around
> in the system, trying to understand where users' jobs and site resources graze.
> Or, you may just try to understand if you are being hit by something like a
> bug. (*)
> you are not alone in this world and others have same troubles as you do ;-).
> Here is a script I wrote to try to get better control over any torque or pbs
> It provides a brief summary of your PBS and Nodes status, along with a job matrix.
> In case you ask, the CPUids are the ones reported at command pbsnodes -a,
> so you may wish to check that its output seems reasonable, before trying qtop.
> It can be particularly useful if you assign colors to your scheduler's policy
> so that you can visually check if your policy is honored; be prepared for
> Generally, I hope it can help you to keep the entropy of a torque system low,
> by giving a fast overview of what is going on.
More information about the torqueusers