[Swift-commit] r2519 - trunk/docs
noreply at svn.ci.uchicago.edu
noreply at svn.ci.uchicago.edu
Mon Feb 9 08:12:57 CST 2009
Author: benc
Date: 2009-02-09 08:12:56 -0600 (Mon, 09 Feb 2009)
New Revision: 2519
Modified:
trunk/docs/userguide.xml
Log:
comment that status.mode=provider does not work with coasters
Modified: trunk/docs/userguide.xml
===================================================================
--- trunk/docs/userguide.xml 2009-02-09 13:49:19 UTC (rev 2518)
+++ trunk/docs/userguide.xml 2009-02-09 14:12:56 UTC (rev 2519)
@@ -2832,14 +2832,39 @@
from workers to the submit side. In <literal>files</literal> mode, a file
indicating success or failure will be created on the site shared filesystem.
In <literal>provider</literal> mode, the execution provider job status will
-be used. Notably, GRAM2 does not return job statuses correctly, and so
-<literal>provider</literal> mode will not work with GRAM2. With other
-providers, it can be used to reduce the amount of filesystem access compared
-to <literal>files</literal> mode. (since Swift 0.8)
+be used.
</para>
+ <para>
+<literal>provider</literal> mode requires the underlying job execution system
+to correctly return exit codes. In at least the cases of GRAM2, and clusters
+used with any provider, exit codes are not returned, and so
+<literal>files</literal> mode must be used in those cases. Otherwise,
+<literal>provider</literal> mode can be used to reduce the amount of
+filesystem access. (since Swift 0.8)
+ </para>
</listitem>
</varlistentry>
+ <varlistentry>
+ <term>
+ <property>ticker.disable</property>
+ </term>
+ <listitem>
+ <para>
+ Valid values: <parameter>true</parameter>, <parameter>false</parameter>
+ </para>
+ <para>
+ Default value: <literal>false</literal>
+ </para>
+
+ <para>
+When set to true, suppresses the output progress ticker that Swift sends
+to the console every few seconds during a run (since Swift 0.9)
+ </para>
+ </listitem>
+ </varlistentry>
+
+
</variablelist>
More information about the Swift-commit
mailing list