[Swift-commit] r6529 - branches/release-0.94/docs/userguide

ketan at ci.uchicago.edu ketan at ci.uchicago.edu
Mon Jun 3 23:22:05 CDT 2013


Author: ketan
Date: 2013-06-03 23:22:04 -0500 (Mon, 03 Jun 2013)
New Revision: 6529

Modified:
   branches/release-0.94/docs/userguide/coasters
   branches/release-0.94/docs/userguide/log-processing
Log:
fixes for bug 1008

Modified: branches/release-0.94/docs/userguide/coasters
===================================================================
--- branches/release-0.94/docs/userguide/coasters	2013-06-03 05:38:54 UTC (rev 6528)
+++ branches/release-0.94/docs/userguide/coasters	2013-06-04 04:22:04 UTC (rev 6529)
@@ -90,3 +90,16 @@
 |remoteMonitorEnabled|If true, show a graphical display of the status of
 the coaster service
 |==================
+
+Submitting to a specific job queue
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+In order to submit to a specific job scheduler queue, the +queue+ parameter of
+coasters sites file should be used. For example, submitting to the +normal+
+queue of a PBS scheduler, one would use the following sites line:
+
+----
+<profile namespace="globus" key="queue">normal</profile>
+----
+
+

Modified: branches/release-0.94/docs/userguide/log-processing
===================================================================
--- branches/release-0.94/docs/userguide/log-processing	2013-06-03 05:38:54 UTC (rev 6528)
+++ branches/release-0.94/docs/userguide/log-processing	2013-06-04 04:22:04 UTC (rev 6529)
@@ -112,18 +112,22 @@
 the "-resume" option. The .rlog file is only for Swift's internal purpose and
 not to be interpreted by the user.
 
-Each line in the log file is typically made up of three parts. The first part
+Each line in the log file typically consists of three parts. The first part
 is the timestamp, the second is the type of log message and the third is the
 message itself. The types of log messages follows the java log4j standard types
-of TRACE, DEBUG, INFO, WARN, ERROR and FATAL. This section lists the various
-Swift log messages and explains the meaning and likely interpretation of those
-messages. Please note that the list is not comprehensive at this time. Also
-note that we will ignore the timestamps here.
+of TRACE, DEBUG, INFO, WARN, ERROR and FATAL.
 
+////
+This section lists the various Swift log messages and explains the meaning and
+likely interpretation of those messages. Note that the list is not
+comprehensive at this time. Also note that we will ignore the timestamps here.
+
 . _DEBUG Loader arguments: [-sites.file, sites.xml, -config, cf, -tc.file, tc, postproc-gridftp.swift]_
+    Swift commandline arguments
 . _DEBUG Loader Max heap: 5592449024_
+    The java runtime heap size
 . _DEBUG textfiles BEGIN_
-. _DEBUG Loader kmlversion is_
+    A dump of config and source files associated with this run
 . _DEBUG VDL2ExecutionContext Stack dump_
 . _INFO  SetFieldValue Set_
 . _INFO  get__site STARTCOMPOUND thread=0-8 name=get__site_
@@ -142,7 +146,9 @@
 . _INFO  ThrottleManager mem=113.54 MB, heap=482.88 MB, maxHeap=5.21 GB_
 . _INFO  ThrottleManager I maxBuffers=512, crtBuffers=0, allowedTransfers=256, active=0, suspended=0_
 . _INFO  PerformanceDiagnosticInputStream [MEM] Heap total: 482.88 MB, Heap used: 118.58 MB_
+Heap sizes for performance
 . _INFO  vdl:execute END_SUCCESS thread=0-8-0 tr=getsite_
+The job ended successfully
 . _INFO  WeightedHostScoreScheduler CONTACT_SELECTED host=localhost, score=99.854_
 . _
-
+////




More information about the Swift-commit mailing list