Job selection
Padb supports many resource managers and should select the appropriate one for your machine, if you have more than one resource manager installed or padb can't detect the correct one use the rmgr configuration option to set machine-wide defaults.If your resource manager or scheduler is not supported you can also use local and process identifiers (pids) will be used instead of job ids.
Resource manager | Name | Notes |
---|---|---|
Any | mpirun | Works with any resource manager or software stack that is compliant with the MPI debugger interface. It is preferable to use support for your specific resource manager if it exists. |
Slurm | slurm | Fully supported |
RMS | rms | Fully supported |
OpenMPI orte | orte | Fully supported |
MPICH2 mpd | mpd | Fully supported in 3.0 and above |
MPICH2 hydra | mpirun | Use the mpirun resource mangager in version 3.2 and above. |
PBS and PBS pro | pbs | Fully supported in 3.2 and above |
None | local | allows process identifiers (pids) to be specified as jobids and treats that process as a single process job. |
None | local-fd | as local but only selects processes which have a certain file open, use the "local-fd-name" configuration option to set the filename. |
None | local-qsnet | as local-fd with local-fd-name set to /proc/qsnet/elan/user to automatically select network jobs on the local node. |
The --list-rmgrs option can be used to show a list of detected resource managers and their active jobs.
Padb provides several ways for the user to select which jobs to target depending on requirements. All jobs detected by padb are identified by a unique numeric "jobid", typically this maps directly only a identifier provided by the underlying resource manager. The default is to target jobs of the current user, this can be over-ridden with the --user flag.