[Swift-commit] r6296 - in trunk/docs: cookbook siteguide userguide utils
ketan at ci.uchicago.edu
ketan at ci.uchicago.edu
Tue Feb 19 21:04:04 CST 2013
Author: ketan
Date: 2013-02-19 21:04:04 -0600 (Tue, 19 Feb 2013)
New Revision: 6296
Modified:
trunk/docs/cookbook/log_processing
trunk/docs/siteguide/futuregrid
trunk/docs/siteguide/intrepid
trunk/docs/siteguide/prereqs
trunk/docs/userguide/log-processing
trunk/docs/utils/gensites.txt
Log:
improvements
Modified: trunk/docs/cookbook/log_processing
===================================================================
--- trunk/docs/cookbook/log_processing 2013-02-19 19:50:13 UTC (rev 6295)
+++ trunk/docs/cookbook/log_processing 2013-02-20 03:04:04 UTC (rev 6296)
@@ -84,7 +84,7 @@
Problem Reporting
~~~~~~~~~~~~~~~~~
-When reporting problems to swift-user at ci.uchicago.edu, please attach the
+When reporting problems to swift-user at ci.uchicago.edu, attach the
following files and information:
. tc.data and sites.xml (or whatever you named these files)
Modified: trunk/docs/siteguide/futuregrid
===================================================================
--- trunk/docs/siteguide/futuregrid 2013-02-19 19:50:13 UTC (rev 6295)
+++ trunk/docs/siteguide/futuregrid 2013-02-20 03:04:04 UTC (rev 6296)
@@ -111,8 +111,8 @@
$ swift -sites.file sites.xml -tc.file tc.data -config cf <yourscript.swift>
-----
-If you would like to create a custom tc file for repeated use, rename it to something other
-than tc.data to prevent it from being overwritten. The sites.xml however will need to be
+If you like to create a custom tc and/or cf file for repeated use, rename it to something other
+than tc.data/cf to prevent it from being overwritten. The sites.xml however will need to be
regenerated every time you start the coaster service. If you need to repeatedly modify some
sites.xml options, you may edit the template in Swift's etc/sites/persistent-coasters. You
may also create your own custom tc files with the hostname of persistent-coasters. More
@@ -132,6 +132,6 @@
More Help
~~~~~~~~~
The best place for additional help is the Swift user mailing list. You can subscribe to this list at
-http://mail.ci.uchicago.edu/mailman/listinfo/swift-user. When submitting information, please send
+http://mail.ci.uchicago.edu/mailman/listinfo/swift-user. When submitting information, send
your sites.xml file, your tc.data, and any error messages you run into.
Modified: trunk/docs/siteguide/intrepid
===================================================================
--- trunk/docs/siteguide/intrepid 2013-02-19 19:50:13 UTC (rev 6295)
+++ trunk/docs/siteguide/intrepid 2013-02-20 03:04:04 UTC (rev 6296)
@@ -165,7 +165,10 @@
Catsn.swift
~~~~~~~~~~~
-The swift script we will run is called catsn.swift. It simply cats a file and saves the result. This is a nice simple test to ensure jobs are running correctly. Create a file called data.txt which contains some simple input - a "hello world" will do the trick.
+The swift script we will run is called catsn.swift. It simply cats a file and
+saves the result. This is a nice simple test to ensure jobs are running
+correctly. Create a file called data.txt which contains some simple input - a
+"hello world" will do the trick.
-----
include::../../examples/misc/catsn.swift[]
@@ -179,13 +182,17 @@
swift -sites.file sites.xml -tc.file tc.data catsn.swift -n=10
-----
-You should see several new files being created, called catsn.0001.out, catsn.0002.out, etc. Each of these
-files should contain the contents of what you placed into data.txt. If this happens, your job has run
-successfully on PADS!
+You should see several new files being created, called catsn.0001.out,
+catsn.0002.out, etc. Each of these files should contain the contents of what
+you placed into data.txt. If this happens, your job has run successfully on
+PADS!
More Help
~~~~~~~~~
-The best place for additional help is the Swift user mailing list. You can subscribe to this list at
-https://lists.ci.uchicago.edu/cgi-bin/mailman/listinfo/swift-user. When submitting information, please send your sites.xml file, your tc.data, and any Swift log files that were created during your attempt.
+The best place for additional help is the Swift user mailing list. You can
+subscribe to this list at
+https://lists.ci.uchicago.edu/cgi-bin/mailman/listinfo/swift-user. When
+submitting information, send your sites.xml file, your tc.data, and any Swift
+log files that were created during your attempt.
Modified: trunk/docs/siteguide/prereqs
===================================================================
--- trunk/docs/siteguide/prereqs 2013-02-19 19:50:13 UTC (rev 6295)
+++ trunk/docs/siteguide/prereqs 2013-02-20 03:04:04 UTC (rev 6296)
@@ -4,5 +4,5 @@
This guide assumes that you have already downloaded and installed Swift.
It assumes that Swift is in your PATH and that you have a working
version of Sun Java 1.5+. For more information on downloading and
-installing Swift, please see the
+installing Swift, see the
http://www.ci.uchicago.edu/swift/guides/release-0.93/quickstart/quickstart.html[Swift Quickstart Guide].
Modified: trunk/docs/userguide/log-processing
===================================================================
--- trunk/docs/userguide/log-processing 2013-02-19 19:50:13 UTC (rev 6295)
+++ trunk/docs/userguide/log-processing 2013-02-20 03:04:04 UTC (rev 6296)
@@ -112,18 +112,20 @@
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
+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_
Modified: trunk/docs/utils/gensites.txt
===================================================================
--- trunk/docs/utils/gensites.txt 2013-02-19 19:50:13 UTC (rev 6295)
+++ trunk/docs/utils/gensites.txt 2013-02-20 03:04:04 UTC (rev 6296)
@@ -142,7 +142,7 @@
WARNING: Running gensites with #app definitions will replace any file
called tc.data in your current directory. If a file called tc.data exists,
it will be renamed to tc.data.old. If you run gensites twice, the original
-contents of your tc.data will be lost. Please either rename your tc file
+contents of your tc.data will be lost. Either rename your tc file
or copy to a different location.
Running Swift With the New Configuration
More information about the Swift-commit
mailing list