[Swift-commit] r5438 - branches/release-0.93/docs/siteguide

[ketan at ci.uchicago.edu]

Author: ketan
Date: 2011-12-18 10:33:15 -0600 (Sun, 18 Dec 2011)
New Revision: 5438

Modified:
   branches/release-0.93/docs/siteguide/beagle
Log:
updating troubleshooting section

Modified: branches/release-0.93/docs/siteguide/beagle
===================================================================
--- branches/release-0.93/docs/siteguide/beagle	2011-12-18 16:20:37 UTC (rev 5437)
+++ branches/release-0.93/docs/siteguide/beagle	2011-12-18 16:33:15 UTC (rev 5438)
@@ -194,4 +194,8 @@
 <workdirectory >/lustre/beagle/ketan/swift.workdir</workdirectory>
 ----
 
+* If the error message does not give much clue, one can go about the following approaches to find more help:
+ - Search for the particular error message on the swift mailing list archive from here: http://www.ci.uchicago.edu/swift/wwwdev/support/index.php
+ - Subscribe to the swift-user lists and post your questions here: https://lists.ci.uchicago.edu/cgi-bin/mailman/listinfo/swift-user
+
 * Application invocation fails. An application invocation might fail for a variety of reasons. Some of the common reasons include a faulty command line, out-of-memory, non-availability of data, library dependencies unmet, among others. In another set of failures, the application invocation might fail for a partial number of datasets. In these conditions, one might want to to continue for the rest of application invocations. In most cases, these conditions could be handled by catching various exitcodes and logging the erroneous invocations for later inspection. In the rest of this section, we provide some such examples.