[padb-devel] [padb] r225 committed - Tabulate the sample output properly, add output for verbose stack...
codesite-noreply at google.com
codesite-noreply at google.com
Thu Sep 10 10:39:19 BST 2009
Revision: 225
Author: apittman
Date: Thu Sep 10 02:38:12 2009
Log: Tabulate the sample output properly, add output for verbose stack
traces. Also change the <a name=> tags to be in divs so the
links go to the absolute location rather than the line before.
http://code.google.com/p/padb/source/detail?r=225
Added:
/trunk/doc/configuration.html
Modified:
/trunk/doc/build_website
/trunk/doc/download.html
/trunk/doc/email.html
/trunk/doc/extensions.html
/trunk/doc/header.html
/trunk/doc/layout.css
/trunk/doc/modes.html
/trunk/doc/upload_website
/trunk/doc/usage.html
=======================================
--- /dev/null
+++ /trunk/doc/configuration.html Thu Sep 10 02:38:12 2009
@@ -0,0 +1,57 @@
+<div id="content">
+
+<h1>Configuration options</h1>
+<i>padb</i> has a number of extended configuration options for tuning
+it's behavior, these can be set in a number of ways. There are options for
+controlling <i>padb</i> itself and how it start up and find jobs and also
+mode specific options which control individual (or multiple) modes.
+<p>
+All configuration options have both a name and a value, in some cases the
value is a comma separated list.
+
+<h3>Setting options</h3>
+
+Configuration options can be set in the following ways:
+<ul>
+<li>Command line</li>
+Use the command-line option <b>--config-option
<key>=<value></b>.
+<b>-O</b> can be substituted for <b>--config-option</b>.
+<li>Environment</li>
+Set the environment variable <b>PADB_<KEY>=<value></b>. All
+environment variables should be specified in upper case.
+<li>Config file</li>
+Config is also loaded from <b>/etc/padb.conf</b> and <b>~/.padbrc</b>.
Contact the
+<a href=email.html>mailing lists</a> for help with these files.
+</ul>
+
+<h3>Viewing active options</h3>
+Running <i>padb</i> with the <b>-v</b> option will show both what options
are being loaded
+and also the used values for all mode specific options.
+
+<h3>Available options</h3>
+A list of configuration options along with their current values can be
+obtained by specifying a key of help with or without a value, i.e. <b>padb
-Ohelp</b>
+
+<h2>Example</h2>
+In normal use the resource manager is selected automatically based on what
is installed, if
+for some reason <i>padb</i> cannot determine the resource manager you are
using you can
+explicitly request one by setting the "rmgr" option.
+<pre class=code>
+ashley at alpha:~$ padb --show-jobs
+Error, multiple resource managers detected, use -Ormgr=<resource
manager>
+orte slurm local-fd local
+ashley at alpha:~$ padb --show-jobs --config-option rmgr=orte
+59315
+ashley at alpha:~$ export PADB_RMGR=orte
+ashley at alpha:~$ padb --show-jobs
+59315
+ashley at alpha:~$
+</pre>
+</div>
+<div id="footer">
+ <hr>
+ <center>
+ <font size=-2>
+ <p>Page maintained by Ashley Pittman. $Date: 2009-09-09 13:25:10 +0100
(Wed, 09 Sep 2009) $ $Revision: 223 $</p>
+ </font>
+ <center>
+</div>
=======================================
--- /trunk/doc/build_website Wed Sep 9 05:25:10 2009
+++ /trunk/doc/build_website Thu Sep 10 02:38:12 2009
@@ -8,7 +8,7 @@
echo Uploading website to http://padb.pittman.org.uk
-FILES="index usage download email extensions modes"
+FILES="index usage download email extensions modes configuration"
TDIR=public
=======================================
--- /trunk/doc/download.html Wed Sep 9 05:29:14 2009
+++ /trunk/doc/download.html Thu Sep 10 02:38:12 2009
@@ -1,10 +1,10 @@
<div id="content">
-<h1>Beta release</h1>
+<a name=beta><h1>Beta release</h1></a>
A <a href="http://padb.googlecode.com/files/padb-3.0-rc1.tgz">3.0 beta
release</a> is on-line at the google downloads section. The target date
for this relese is 19-8-09.
-<h1>Current stable release</h1>
+<a name=stable><h1>Current stable release</h1></a>
The latest stable release, <a
href=http://padb.googlecode.com/files/padb-2.5.tgz title="Download 2.5
release">2.5</a> can be downloaded direct from the google downloads section.
@@ -18,7 +18,7 @@
<a href=http://code.google.com/p/padb/downloads/list>downloads</a> section.
-<h3>Quadrics release</h3>
+<h4>Quadrics release</h4>
The latest stable release from Quadrics is version 2.2 was made on the 16th
March 2009 and at the time of writing is downloadable from their
@@ -26,7 +26,7 @@
</a> in the QSNET2LIBS package. No further releases are expected
from quadrics at this time.
-<h1>Development and Subversion access</h1>
+<a name=svn><h1>Development and Subversion access</h1></a>
Subversion access to <i>padb</i> is hosted by
<a href=http://code.google.com/p/padb/>google</a> where you can
<a href=http://code.google.com/p/padb/source/browse/trunk>browse the
=======================================
--- /trunk/doc/email.html Wed Sep 9 04:11:59 2009
+++ /trunk/doc/email.html Thu Sep 10 02:38:12 2009
@@ -9,7 +9,7 @@
<li><a
href=http://pittman.org.uk/mailman/listinfo/padb-devel_pittman.org.uk>
padb-devel</a> (<a
href=http://pittman.org.uk/pipermail/padb-devel_pittman.org.uk/>archives</a>)
for discussion of ongoing development of padb, feature requests and
technical discussion</li>
<li><a
href=http://pittman.org.uk/mailman/listinfo/padb-users_pittman.org.uk>
-padb-users</a> (<a
href=http://pittman.org.uk/pipermail/padb-users_pittman.org.uk/>archives</a>)for
discussion on the use of padb and general questions.</li>
+padb-users</a> (<a
href=http://pittman.org.uk/pipermail/padb-users_pittman.org.uk/>archives</a>)
for discussion on the use of padb and general questions.</li>
</ul>
</div>
<div id="footer">
=======================================
--- /trunk/doc/extensions.html Wed Sep 9 04:11:59 2009
+++ /trunk/doc/extensions.html Thu Sep 10 02:38:12 2009
@@ -1,7 +1,10 @@
<div id="content">
<h2>MPI collective debugger extension proposal</h2>
-<h3>Overview</h3>
+<div class=mode>
+ <a name=overview></a>
+ <h3>Overview</h3>
+</div>
The current
<a href="http://www.mcs.anl.gov/research/projects/mpi/mpi-debug/">MPI
debugger interface</a>
is used to export information from a running application to a debugger.
The current
@@ -101,7 +104,10 @@
This extension was originally developed in early 2007 whilst I was working
at
Quadrics and has proved it's value numerous times in real-life cases.
-<h2>Sample Implementation</h2>
+<div class=mode>
+ <a name=open-mpi></a>
+ <h2>Sample Implementation</h2>
+</div>
At this time a sample implementation is available for OpenMPI only
although work
is being done a MPICH2 version.
=======================================
--- /trunk/doc/header.html Wed Sep 9 05:25:10 2009
+++ /trunk/doc/header.html Thu Sep 10 02:38:12 2009
@@ -22,9 +22,9 @@
<br><a href="usage.html#job" title="Selecting a job">Jobs</a>
<br><a href="usage.html#rank" title="Selecting ranks within a
job">Ranks</a>
<br><a href="usage.html#full-report" title="Generating a full report
for a job">Full Report mode</a>
- <br><a href="usage.html#config" title="Setting configuration
options">Configuration</a>
+ <br><a href="configuration.html" title="Setting configuration
options">Configuration</a>
</font>
- <li><a href="modes" title="Modes of operation">Modes of operation</a>
+ <li><a href="modes.html" title="Modes of operation">Modes of
operation</a>
<font size=-1
<br><a href="modes.html#proc-summary" title="Process summary">Process
state</a>
<br><a href="modes.html#proc-info" title="Process info">Process state
(verbose)</a>
@@ -35,7 +35,16 @@
<br><a href="modes.html#mpi-watch" title="Job monitoring">Job
monitoring
</font>
<li><a href="download.html" title="Download page">Download</a>
+ <font size=-1
+ <br><a href="download.html#beta" title="Latest development
release">Beta 3.0</a>
+ <br><a href="download.html#stable" title="Latest stable
release">Stable 2.5</a>
+ <br><a href="download.html#svn" title="Source code access">Source
code</a>
+ </font>
<li><a href="extensions.html" title="Proposed MPI extensions">Patches</a>
+ <font size=-1
+ <br><a href="extensions.html#overview" title="Proposal
description">Overview</a>
+ <br><a href="extensions.html#open-mpi" title="OpenMPI patch">OpenMPI
patch</a>
+ </font>
<li><a href="email.html" title="Contact information">Mailing lists</a>
</font>
</ul>
=======================================
--- /trunk/doc/layout.css Wed Sep 9 05:25:10 2009
+++ /trunk/doc/layout.css Thu Sep 10 02:38:12 2009
@@ -19,8 +19,26 @@
table.news {
background-color: #FFFFA0;
}
+
+table.example {
+ margin: 2em;
+ padding: 1em;
+ background-color: #707070;
+}
+
+table.rmgrs {
+ background-color: #f0f0f0;
+}
#footer {
clear: both;
}
+pre.code {
+#margin-left: 2em;
+#margin-right: 2em;
+background-color: #f0f0f0;
+padding: 10px;
+border: 1px solid;
+}
+
=======================================
--- /trunk/doc/modes.html Wed Sep 9 04:11:59 2009
+++ /trunk/doc/modes.html Thu Sep 10 02:38:12 2009
@@ -12,7 +12,7 @@
into a single status report for the job. For modes where information is
process specific a number of options are offered to reduce the amount of
information displayed to the screen. Without any of these options
specified
-<i>padb</i> will prefix each line of output with the vpid followed by a
colon ": ".
+<i>padb</i> will prefix each line of output with the rank followed by a
colon ":".
The <b>--compress-long</b> option will print a header for each process and
display the information for that rank below the header without any
per-line prefix.
The <b>--compress</b> option will do the same however will also attempt to
merge
@@ -34,16 +34,24 @@
<p>
All examples on this page show <i>padb</i> targeting a single specific
job, either by providing a number <i>job identifier</i>
-on the command line or via the <b>--all</b> or <b>--any</b> options. See
<a href=/usage>usage</a> page for information
+on the command line or via the <b>--all</b> or <b>--any</b> options. See
<a href=usage.html>usage</a> page for information
on selecting which jobs.
-<a name=proc-summary><h2>Process state</h2></a>
+<div class=mode>
+ <a name=proc-summary></a>
+ <h2>Process state</h2>
+</div>
The <b>--proc-summary</b> mode shows basic information about running
processes, presented one process per line. Users can control which
information
is shown using the <b>--proc-format</b> option.
-<table border=1>
+<table class=example>
<tr><td>
-<pre>
+<pre class=code>
+$ padb --all --proc-summary
+</pre>
+<tr/><td/>
+<tr><td>
+<pre class=code>
vpid hostname pid vmsize vmrss S %cpu command
7 i3 2623 160336 kB 4464 kB R 49 a.out
6 i2 2616 160336 kB 4464 kB R 48 a.out
@@ -59,15 +67,22 @@
The config option <b>proc-sort-key</b> controls which column the table is
sorted by, the default is vpid.
-<a name=proc-info><h3>Per-process process state</h3></a>
-
+<div class=mode>
+ <a name=proc-info></a>
+ <h3>Per-process process state</h3>
+</div>
The <b>--proc-info</b> mode reports a much more complete report about the
state of the process but doesn't easily reduce
when run across multiple ranks. It can be controlled by the
<b>proc-shows-proc</b> (default: 1), <b>proc-shows-task</b>
(default: 0), <b>proc-shows-fds</b> (default:1 ) and
<b>proc-shows-maps</b> (default: 0) configuration options. This output
also shows possible columns when running in "Process state" mode.
-<table border=1>
+<table class=example>
<tr><td>
-<pre>
+<pre class=code>
+$ padb --all --rank=0 --proc-info
+</pre>
+<tr/><td/>
+<tr><td>
+<pre class=code>
hostname:fnarp
exe:/home/ashley/IMB/imb/src/IMB-MPI1
Name: IMB-MPI1
@@ -126,14 +141,21 @@
</tr></td>
</table>
-
-<a name=stack-trace><h2>Stack traces</h2></a>
+<div class=mode>
+ <a name=stack-trace></a>
+ <h2>Stack traces</h2>
+</div>
The <b>--stack-trace</b> option, best used as shown here with the
<b>--tree</b> option
shows stack traces for each process in the job. Stack traces are
shown "backwards" with main()
at the top to facilitate the tree view shown here.
-<table border=1>
+<table class=example>
<tr><td>
-<pre>
+<pre class=code>
+$ padb --all --stack-trace --tree
+</pre>
+<tr/><td/>
+<tr><td>
+<pre class=code>
-----------------
[0-1] (2 processes)
-----------------
@@ -168,8 +190,78 @@
</table>
The config options <b>stack-shows-locals</b> and <b>stack-shows-params</b>
can be enabled to display more information in the stack
-trace, these are disabled by default and make the tree based reporting
very difficult so are best used in conjunction with the
-<b>--rank</b> option.
+trace, these are disabled by default and make the tree based reporting
very difficult so are best used in conjunction with the <b>--rank</b>
option as shown here.
+
+<table class=example>
+<tr><td>
+<pre class=code>
+$ padb --any --stack-trace --rank 0 -O stack-shows-locals=1
-Ostack-shows-params=1
+</pre>
+<tr/><td/>
+<tr><td>
+<pre class=code>
+main() at ?:?
+PMPI_Barrier() at
/mnt/home/ashley/mpich2/mpich2-1.1.1p1/src/mpi/coll/barrier.c:421
+ params:
+ MPI_Comm comm = -2080374780
+ locals:
+ MPICH_PerThread_t * MPIR_Thread = (MPICH_PerThread_t *) 0x80e9740
+ int mpi_errno = 10001568
+ MPID_Comm * comm_ptr = (MPID_Comm *) 0x80da8e0
+MPIR_Barrier_or_coll_fn() at
/mnt/home/ashley/mpich2/mpich2-1.1.1p1/src/mpi/coll/barrier.c:244
+ params:
+ MPID_Comm * comm_ptr = (MPID_Comm *) 0x198
+ locals:
+ int mpi_errno = 0
+MPIR_Barrier() at
/mnt/home/ashley/mpich2/mpich2-1.1.1p1/src/mpi/coll/barrier.c:75
+ params:
+ MPID_Comm * comm_ptr = (MPID_Comm *) 0x80da9e8
+ locals:
+ int size = 8
+ int rank = 0
+ int mask = 1
+ int mpi_errno = <value optimized out>
+ MPI_Comm comm = -2080374779
+MPIC_Sendrecv() at
/mnt/home/ashley/mpich2/mpich2-1.1.1p1/src/mpi/coll/helper_fns.c:163
+ params:
+ void * sendbuf = (void *) 0x0
+ int sendcount = 0
+ MPI_Datatype sendtype = 1275068685
+ int dest = 1
+ int sendtag = 1
+ void * recvbuf = (void *) 0x0
+ int recvcount = 0
+ MPI_Datatype recvtype = 1275068685
+ int source = 7
+ int recvtag = 1
+ MPI_Comm comm = -2080374779
+ MPI_Status * status = (MPI_Status *) 0x1
+ locals:
+ MPID_Request * recv_req_ptr = (MPID_Request *) 0x80e9ac0
+ MPID_Request * send_req_ptr = (MPID_Request *) 0x80e9c94
+ int mpi_errno = <value optimized out>
+ MPID_Comm * comm_ptr = (MPID_Comm *) 0x80da9e8
+MPIC_Wait() at
/mnt/home/ashley/mpich2/mpich2-1.1.1p1/src/mpi/coll/helper_fns.c:404
+ params:
+ MPID_Request * request_ptr = (MPID_Request *) 0x80e9ac0
+ locals:
+ MPID_Progress_state progress_state = {ch = {completion_count = 16}}
+ int mpi_errno = 134869472
+MPIDI_CH3I_Progress() at
/mnt/home/ashley/mpich2/mpich2-1.1.1p1/src/mpid/ch3/channels/nemesis/nemesis/include/mpid_nem_inline.h:1088
+ params:
+ MPID_Progress_state * progress_state = (MPID_Progress_state *)
0xbfc69eec
+ int is_blocking = 1
+ locals:
+ MPID_nem_fbox_mpich2_t * pbox = (MPID_nem_fbox_mpich2_t *) 0x80
+ unsigned int completions = 16
+ int mpi_errno = <value optimized out>
+ int complete = -1077502728
+ int pollcount = 0
+sched_yield() at ?:?
+__kernel_vsyscall() at ?:?
+</pre>
+</tr></td>
+</table>
<p>
Stack traces on Linux often show functions below main(), these are
automatically stripped unless the flag
@@ -179,17 +271,25 @@
<h2>MPI Specific modes</h3>
-<a name=mpi-queue><h3>MPI message queues</h3></a>
-<a name=message-queue></a>
+<div class=mode>
+ <a name=mpi-queue></a>
+ <a name=message-queue></a>
+ <h3>MPI message queues</h3>
+</div>
The option <b>--mpi-queue</b> will tell <i>padb</i> to read the MPI message
queues from your application if possible. Here shown with the
<b>--compress</b> option.
<p>
The option <b>--message-queue</b> shows the tport queues on QsNet
systems. On non-QsNet systems it automatically falls back
to <b>--mpi-queue</b>.
-<table border=1>
+<table class=example>
<tr><td>
-<pre>
+<pre class=code>
+$ padb --all --compress --mpi-queue
+</pre>
+<tr/><td/>
+<tr><td>
+<pre class=code>
----------------
0
----------------
@@ -260,12 +360,20 @@
</tr></td>
</table>
-<a name=deadlock><h3>Collective information</h3></a>
-If you are using a <a href=/extensions>patched MPI library</a> it's also
possible for <i>padb</i> to
+<div class=mode>
+ <a name=deadlock></a>
+ <h3>Collective information</h3>
+</div>
+If you are using a <a href=extensions.html>patched MPI library</a> it's
also possible for <i>padb</i> to
display the state of collective operations across your job using the
<b>--deadlock</b> mode.
-<table border=1>
+<table class=example>
<tr><td>
-<pre>
+<pre class=code>
+$ padb --all --deadlock
+</pre>
+<tr/><td/>
+<tr><td>
+<pre class=code>
Information for group '0x4' (MPI COMMUNICATOR 4 DUP FROM 0)
Group members [1-3] (size 4) are in call 2 to Barrier.
Group member 0 (size 4) has completed call 1 to Barrier.
@@ -279,7 +387,10 @@
</tr></td>
</table>
-<a name=kill><h3>Signal delivery</h2></a>
+<div class=mode>
+ <a name=kill></a>
+ <h3>Signal delivery</h2>
+</div>
To deliver signals to processes in a job use the <b>--kill</b> mode
together with the optional
<b>--signal=<name></b> option. No output is produced by this mode.
@@ -287,7 +398,10 @@
The <b>--set-debug</b>, <b>--group</b> and <b>--statistics</b> modes are
QsNet specific. The <b>--deadlock</b> mode
performs the same function as <b>--group</b> for MPI programs.
-<a name=mpi-watch><h2>Process watch</h2></a>
+<div class=mode>
+ <a name=mpi-watch></a>
+ <h2>Process watch</h2>
+</div>
The <b>--mpi-watch</b> mode in <i>padb</i> will cause padb to inspect the
parallel job and write a single
line of output to the screen, each character representing a process in the
parallel job. Each character
has a different value depending on the state of that process at the time
of sampling. This provides a quick
@@ -299,9 +413,14 @@
to see progress of the application over time, this trace shows the popular
IMB benchmarking application, those
familiar with it will immediately see the different stages of benchmark
and how each stage uses more and more processes
over time with any unused ones blocking in MPI_Barrier.
-<table border=1>
+<table class=example>
<tr><td>
-<pre>
+<pre class=code>
+$ padb --all --mpi-watch -Owatch-clears-screen=0 -Ointerval=5
+</pre>
+<tr/><td/>
+<tr><td>
+<pre class=code>
u: unexpected messages U: unexpected and other messages
s: sending messages r: receiving messages m: sending and receiving
b: Barrier B: Broadcast g: Gather G: AllGather r: reduce: R: AllReduce
=======================================
--- /trunk/doc/upload_website Wed Sep 9 04:37:49 2009
+++ /trunk/doc/upload_website Thu Sep 10 02:38:12 2009
@@ -11,7 +11,7 @@
# Load the password from a non-public file ;)
. ~/padb-website-password.txt
-FILES="index usage download email extensions modes"
+FILES="index usage download email extensions modes configuration"
ftp-upload --host padb.pittman.org.uk -u padb at pittman.co.uk --password
$PASSWORD layout.css
=======================================
--- /trunk/doc/usage.html Wed Sep 9 05:25:10 2009
+++ /trunk/doc/usage.html Thu Sep 10 02:38:12 2009
@@ -1,19 +1,72 @@
<div id="content">
<h1>Job selection</h1>
-<a name=rmgr><h2>Selecting the Resource Manager (Job Launcher)</h2></a>
+<div class=mode>
+ <a name=rmgr></a>
+ <h2>Selecting the Resource Manager (Job Launcher)</h2>
+</div>
<i>Padb</i> supports many resource managers and should select
the appropriate one for your cluster, if you have more than
one resource manager installed or <i>padb</i> can't detect
-the correct one use the <b>rmgr</b> <a href=#config>configuration
option</a>.
+the correct one use the <b>rmgr</b> <a
href=configuration.html>configuration option</a>.
<p>If no resource manager is found you can use <b>-O rmgr=local</b> and
process
identifiers (pids) will be used instead of job ids.
+
+<center>
+<table class=rmgrs border=1 width=90%>
+ <tr>
+ <th>Resource manager</th>
+ <th>Name</th>
+ <th>Notes</th>
+ </tr>
+ <tr>
+ <td>Slurm</td>
+ <td>slurm</td>
+ <td>Fully supported</td>
+ </tr>
+ <tr>
+ <td>RMS</td>
+ <td>rms</td>
+ <td>Fully supported</td>
+ </tr>
+ <tr>
+ <td>OpenMPI orte</td>
+ <td>orte</td>
+ <td>Fully supported</td>
+ </tr>
+ <tr>
+ <td>MPICH2/mpd</td>
+ <td>mpd</td>
+ <td>Fully supported in 3.0 and above</td>
+ </tr>
+ <tr>
+ <td>None</td>
+ <td>local</td>
+ <td>allows process identifiers (pids) to be specified as jobids and
treats that process
+as a single process job.</td>
+ </tr>
+ <tr>
+ <td>None</td>
+ <td>local-fd</td>
+ <td>as local but only selects processes which have a certain file open,
use the "local-fd-name" configuration option to set the filename.</td>
+ </tr>
+ <tr>
+ <td>None</td>
+ <td>local-qsnet</td>
+ <td>as local-fd with local-fd-name set to /proc/qsnet/elan/user to
automatially select network jobs on the local node.</td>
+ </tr>
+</table>
+</center>
+
<p>The <b>--list-rmgrs</b> option can be used to show a list of detected
resource managers and their active jobs.
-<a name=job><h2>Selecting the job(s) to target</h2></a>
+<div class=mode>
+ <a name=job></a>
+ <h2>Selecting the job(s) to target</h2>
+</div>
<i>Padb</i> 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
@@ -38,7 +91,10 @@
To target a specific job specify the jobid for the job on the command line,
after all other options.
-<a name=full-report</a><h3>To target a specific job (Full report
option)</h3>
+<div class=mode>
+ <a name=full-report</a></a>
+ <h3>To target a specific job (Full report option)</h3>
+</div>
If trying to diagnose a problem or gather information there is another
option, <b>--full-report=<jobid></b>, this tells padb to target the
job
specified and to report all information about the job it knows how to
@@ -60,7 +116,10 @@
the exception of Full Report only one mode can be selected, if you need
more information about the program run <i>padb</i> more than once.
-<a name=full-report><h2>Full Report</h2></a>
+<div class=mode>
+ <a name=full-report></a>
+ <h2>Full Report</h2>
+</div>
If you are just starting with <i>padb</i> or are creating an error
report for somebody else then the <b>--full-report=<jobid></b>
option is a good place
to start, this will complete a full diagnostic report for the job
@@ -69,44 +128,8 @@
<p>
-A list of avaliable modes and their descriptions can be found on the <a
href=/modes>modes</a> page.
-
-<hr>
-
-<a name=config></a><h1>Configuration options</h1>
-<i>padb</i> has a number of extended configuration options for tuning
-it's behavior, these can be set in a number of ways. All configuration
-options are key/value pairs.
-<ul>
-<li>Command line</li>
-Use the command-line option <b>--config-option
<key>=<value></b>.
-<b>-O</b> can be substituted for <b>--config-option</b>.
-<li>Environment</li>
-Set the environment variable <b>PADB_<KEY>=<value></b>. All
-environment variables should be specified in upper case.
-<li>Config file</li>
-Config is also loaded from <b>/etc/padb.conf</b> and <b>~/.padbrc</b>.
Contact the
-<a href=/email>mailing lists</a> for help with these files.
-</ul>
-A list of configuration options along with their current values can be
-obtained by specifying a key of help with or without a value, i.e. <b>padb
-Ohelp</b>
-
-<h2>Example</h2>
-<table border=1>
-<tr><td>
-<pre>
-ashley at alpha:~$ padb --show-jobs
-Error, multiple resource managers detected, use -Ormgr=<resource manager>
-orte slurm local-fd local
-ashley at alpha:~$ padb --show-jobs --config-option rmgr=orte
-59315
-ashley at alpha:~$ export PADB_RMGR=orte
-ashley at alpha:~$ padb --show-jobs
-59315
-ashley at alpha:~$
-</pre>
-</td></tr>
-</table>
+A list of avaliable modes and their descriptions can be found on the <a
href=modes.html>modes</a> page.
+
</div>
<div id="footer">
<hr>
More information about the padb-devel
mailing list