<html><head><style type='text/css'>p { margin: 0; }</style></head><body><div style='font-family: Times New Roman; font-size: 12pt; color: #000000'>Matthew,<div><br></div><div>When the first token in the coaster jobmanager parameter is "local" as in "local:pbs", then the coaster server threads run inside the main swift JVM, and thus log to the main swift log. thats the file with the long name starting with your swift script file name, followed by a timestamp and unique ID, and ending in .log.</div><div><br></div><div>All the log entries that you'd find in the coaster.log file should, I think, be in the main log.</div><div><br></div><div>- Mike</div><div> <br><br><hr id="zwchr"><blockquote style="border-left:2px solid rgb(16, 16, 255);margin-left:5px;padding-left:5px;"><br>When running with coasters using the gt2:gt2:pbs provider, an excellent log file pops up in<br> ~/.globus/coasters/coasters.log<br>containing useful lines like:<br> DEBUG TaskImpl Task(type=JOB_SUBMISSION, identity=urn:...<br>
<br>This file isn't generated when using the local:pbs provider, at least out-of-box.<br><br>Is there a way to turn that output log file back on, or to get those debug lines in the Swift job log file, using the local:pbs provider?<br>
<br>Thanks for your time,<br><br>Matthew<br><br><br><br>
<br>_______________________________________________<br>Swift-user mailing list<br>Swift-user@ci.uchicago.edu<br>http://mail.ci.uchicago.edu/mailman/listinfo/swift-user</blockquote><br><span><br><br>-- <br><span name="x"></span>Michael Wilde<br>Computation Institute, University of Chicago<br>Mathematics and Computer Science Division<br>Argonne National Laboratory<br><span name="x"></span><br></span></div></div></body></html>