Commit f4c55c77 authored by Leigh B. Stoller's avatar Leigh B. Stoller

Minor updates to startcmd documentation as per Jay's request.

parent 3f56ba9b
......@@ -328,7 +328,7 @@ tb-set-node-rpms $node0 rpm1 rpm2 rpm3
<pre>
tb-set-node-startcmd <i>node</i> <i>startupcmd</i>
tb-set-node-startcmd $node0 {mystart.sh -a >& /tmp/node0.log}
tb-set-node-startcmd $node0 "mystart.sh -a >& /tmp/node0.log"
</pre>
<p>Notes:
......
......@@ -628,14 +628,16 @@ be unpacked in, all separated by spaces.
You can start your application automatically when your nodes boot by
using the <tt>tb-set-node-startcmd</tt> NS extension. The argument is
the pathname of a script or program that is run as the <tt>UID</tt> of
the experiment creator, after the node has reached multiuser mode. You
can specify the same program for each node, or a different program.
For example:
a command string (pathname of a script or program, plus arguments)
that is run as the <tt>UID</tt> of the experiment creator, after the
node has reached multiuser mode. The command is invoked using
<tt>/bin/csh</tt>, and the working directory is undefined (your script
should cd to the directory you need). You can specify the same program
for each node, or a different program. For example:
<code><pre>
tb-set-node-startcmd $nodeA /proj/pid/runme.nodeA
tb-set-node-startcmd $nodeB /proj/pid/runme.nodeB </code></pre>
tb-set-node-startcmd $nodeA "/proj/pid/runme.nodeA"
tb-set-node-startcmd $nodeB "/proj/pid/runme.nodeB" </code></pre>
will run <tt>/proj/pid/runme.nodeA</tt> on nodeA and
<tt>/proj/pid/runme.nodeA</tt> on nodeB. The programs must reside on
......@@ -648,7 +650,7 @@ output into a file. You can place the file on the local node, or in
one of the NFS mounted directories mentioned above. For example:
<code><pre>
tb-set-node-startcmd $nodeB /proj/pid/runme >& /tmp/foo.log </code></pre>
tb-set-node-startcmd $nodeB "/proj/pid/runme >& /tmp/foo.log" </code></pre>
The exit value of the start command is reported back to the Web
Interface, and is made available to you via the "Experiment
......@@ -1027,7 +1029,7 @@ does not exit from its start command until all of the nodes have
finished. A dummy start command can be setup like this:
<code><pre>
tb-set-node-startcmd $nodeC /bin/echo </code></pre>
tb-set-node-startcmd $nodeC "/bin/echo" </code></pre>
<p>
The status of your batch experiment can be viewed via the "Experiment
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment