<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Mike-<div><br></div><div>My initial reaction is that a fix would probably not be doable in the next few days, since it would almost certainly require scheduling downtime to bring Cobalt down, apply the fix, test, and restart. But I'll ping the Cobalt folks to find out how feasible this would be. My recollections from my previous investigation is that it would require changes to the cluster_system component as well as the launcher, so a shutdown wouldn't be avoidable.</div><div><br></div><div>-Andrew</div><div><br><div><div>On Jan 11, 2011, at 4:48 PM, Michael Wilde wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "><span class="Apple-style-span" style="font-family: monospace; ">Hi ALCF Team,<br><br>The following known issue in Cobalt is currently preventing us from running Swift on Eureka:<br><br> <a href="http://trac.mcs.anl.gov/projects/cobalt/ticket/462">http://trac.mcs.anl.gov/projects/cobalt/ticket/462</a><br><br>With some additional development effort we can work around this, but it would be much cleaner and better if this were fixed in Cobalt, instead, as suggested in ticket 462 above.<br><br>Is there any chance that can be done in the next few days?<span class="Apple-converted-space"> </span><br>If not, please let me know, and we will implement the work-around instead.<br><br>This is holding up work on the DOE ParVis project (Rob Jacob, PI) and we've had to move some work we want to run on Eureka to other platforms in the meantime.<br><br>Thanks very much,<br><br>Mike<br><br>462 is:<br><br>Ticket #462 (new defect)<br>Opened 7 months ago<br>Cobalt on clusters ignores job script arguments<br><br>Reported by:<span class="Apple-tab-span" style="white-space: pre; "> </span>acherry<span class="Apple-tab-span" style="white-space: pre; "> </span><br>Priority:<span class="Apple-tab-span" style="white-space: pre; "> </span><span class="Apple-converted-space"> </span>major<span class="Apple-tab-span" style="white-space: pre; "> </span><br>Component:<span class="Apple-tab-span" style="white-space: pre; "> </span><span class="Apple-converted-space"> </span>clients<br><span class="Apple-tab-span" style="white-space: pre; "> </span><br>Description<span class="Apple-converted-space"> </span><br><br>It appears that cobalt-launcher.py does not support running a job script or executable with command arguments, even though qsub will accept the arguments, and the man page and help for qsub indicates that arguments are accepted.<br><br>I'm filing this as a bug rather than a feature request, since the behavior isn't consistent with the documentation. But I'd rather the fix for this to be adding support for args, rather than changing the docs to say they aren't accepted. :-)<br></span></span></blockquote></div><br></div></body></html>