IPP Software Navigation Tools IPP Links Communication Pan-STARRS Links

Ignore:
Timestamp:
Aug 8, 2005, 10:17:52 PM (21 years ago)
Author:
eugene
Message:

fleshed out psched/pcontrol/pclient descriptions

File:
1 edited

Legend:

Unmodified
Added
Removed

  • trunk/Ohana/doc/www/html/IPP-subsystems/pclient/index.htm

    r4727 r4732  
    33<meta name=page  content=pclient summary>
    44
    5 pclient is the remote process monitor
     5#pclient/# is the remote process monitor for pcontrol, the parallel
     6process controller.
     7
     8<h3>Overview</h3>
     9
     10<p>
     11The program #pclient/# is used to support the remote jobs which are
     12run on the remote hosts by #pcontrol/#.  The concept of pclient is to
     13act as a buffer between the job running on the remote host and
     14pcontrol.  The pcontrol design uses (by default) ssh connections
     15initiated by pcontrol to the remote hosts.  These connections execute
     16the remote program of pclient.  The use of a remote login process lets
     17the UNIX system take care of the user authentication issues.  In this
     18case, the recommended practice is to set up ssh to allow the
     19connection to the remote host without additional authentication using
     20the appropriate authorized keys (see <a href=ssh-issues>this
     21article<a> on ssh issues). 
     22
     23<p>
     24It is convenient to keep a continuous connection to the remote hosts.
     25This avoids incurring the overhead of authentication for each command
     26which is executed, while keeping a high-quality user authentication
     27process in place. 
     28
     29<p>
     30pclient acts as a buffer between pcontrol and the remote background
     31process, allowing the continuous connection to remain viable without
     32samping pcontrol with output from the jobs. 
     33
     34<h3>Commands</h3>
     35
     36<p>
     37pclient has a very limited command set, as follows:
     38<ul>
     39<li> job (command) : start the job (UNIX command) in the background.
     40<li> check         : return the current job status
     41<li> status        : return the current job status (?)
     42<li> stdout        : dump the stdout stream accumulated from the job
     43back to the calling program.
     44<li> stderr        : dump the stderr stream accumulated from the job
     45back to the calling program.
     46<li> reset         : kill (if needed) the job and reset to accept
     47another job.
     48</ul>
     49
Note: See TracChangeset for help on using the changeset viewer.