Changes between Version 2 and Version 3 of pantasks_controller_interactions

Timestamp:

Oct 4, 2012, 1:13:43 PM (14 years ago)

Author:

eugene

Comment:

--

pantasks_controller_interactions

@@ -26 +26 @@
 
 check on the status of a single job or host.  the jobID or hostID is
-an integer value [1].  The return is a block of information giving the
+an integer value^1^.  The return is a block of information giving the
 status and some other infomation.  
 
@@ -48 +48 @@
 where:
 
- * (status) is one of PENDING, BUSY, DONE, EXIT, CRASH
- * (Nexit) is the exit status of the command (ie, as if it were run on
-        the UNIX command line).
- *(Nbytes) is the size of the standard out and standard error buffers
-         from the job
- *(elapsed time) is the number of seconds it took to run the command;
-         this is only set on exit.
+  * (status) is one of PENDING, BUSY, DONE, EXIT, CRASH
+  * (Nexit) is the exit status of the command (ie, as if it were run on the UNIX command line).
+  * (Nbytes) is the size of the standard out and standard error buffers from the job
+  * (elapsed time) is the number of seconds it took to run the command; this is only set on exit.
 
  * exit
@@ -101 +98 @@
   * IDLE : machines which are currently unoccupied with processing
   * BUSY : machines which are currently active
-  * RESP : machines which are currently active and responding to
-           another command
-  * DONE : machines which have completed a job, but are not yet ready
-           to accept a new job.
-  * DOWN : machines which are currently unresponsive (pcontrol will
-           try to reconnect after an interval)
+  * RESP : machines which are currently active and responding to another command
+  * DONE : machines which have completed a job, but are not yet ready to accept a new job.
+  * DOWN : machines which are currently unresponsive (pcontrol will try to reconnect after an interval)
   * OFF  : machines which are currently off (pcontrol will not try to reconnect)
 
@@ -119 +113 @@
   * BUSY    : job is running on a host
   * RESP    : job is running on a host, and responding to another command
-  * DONE    : job has finished, but its completion state has not yet
-              been assessed
+  * DONE    : job has finished, but its completion state has not yet been assessed
   * EXIT    : job finished with a valid exit status (ie, no abort or segfault)
   * CRASH   : job aborted or segfaulted
   * KILL    : kill has been requested for the job
 
-* machines : list the status of the hosts by unique machine name.
+ * machines : list the status of the hosts by unique machine name.
   This command is one of the few which work with the multiple
   connections to a single named machine as the same connection.  The
@@ -155 +148 @@
  * run : set the run level for the controller.  the command is of the
    form "run (level)".  pcontrol may be in one of 4 run levels: 
-   * all : all normal pcontrol ops (this is aslo set with no optional
-           argument to the run command).
-   * reap : keep the machines running (maintain comms and turn on/off
-            as needed) and harvest results from jobs, but do not spawn
-            new jobs.
-   * hosts : manage the machines, but do not manage jobs (spawn or
-             harvest).
+   * all : all normal pcontrol ops (this is aslo set with no optional argument to the run command).
+   * reap : keep the machines running (maintain comms and turn on/off as needed) and harvest results from jobs, but do not spawn new jobs.
+   * hosts : manage the machines, but do not manage jobs (spawn or harvest).
    * none  : stop all pcontrol processing
 
- * status : report the current status of the controller: list all
-   known jobs and all known hosts, giving their status.
+ * status : report the current status of the controller: list all known jobs and all known hosts, giving their status.
 
  * stop : stop all pcontrol processing (equivalent to "run none")
 
- * verbose : turn on verbose mode for pcontrol (output to pcontrol.log
-   or use "controller output").
+ * verbose : turn on verbose mode for pcontrol (output to pcontrol.log or use "controller output").
 
  * version : print version info for pcontrol
 
- * pulse : in non-threaded pcontrol mode (deprecated), set the
-   readline timeout.
+ * pulse : in non-threaded pcontrol mode (deprecated), set the readline timeout.
   
 
-[1] : note that the command 'controller status' includes the job and
+^1^ : note that the command 'controller status' includes the job and^
 host ID values in the form X.X.X.X where X is a hexidecimal number.
 Unfortunately, pcontrol does not understand this format for the IDs