<HTML>
<HEAD>
<TITLE>Non-cummulative pbsnodes -o command</TITLE>
</HEAD>
<BODY>
<FONT FACE="Verdana, Helvetica, Arial"><SPAN STYLE='font-size:12.0px'>This is probably a fairly basic beef about Torque but it has been bugging the hell out of me. <BR>
<BR>
When using the command “pbsnode –o –N ‘message’ node1 node2 ...” to drain nodes, we have to list all the nodes that we want to stay drained in that single command ie.: even if a node was previously drained for another reason, issuing a “pbsnode –o” command without specifying the previously drained nodes results in those nodes being marked online instead of offline. <BR>
<BR>
This is truly ridiculous, it’s like playing a game of bonk the gopher. It is conceivable to have more nodes that you would want drained then can be specified on a single line and there should be no reason for us to have to independently track what nodes should be offline. <BR>
<BR>
As near as I can tell, most people avoid this with creative workarounds such as shutting down the pbs_mom daemon on the nodes to be offline or by creating very specific reservations. I’d imagine that there may be more such creative workarounds spurring more diversity in operational practices.<BR>
<BR>
So the question is, how do you work around this ridiculous behaviour at your site and is there any valid technical reason for pbsnodes to work in this fashion?<BR>
<BR>
Regards,<BR>
John</SPAN></FONT>
</BODY>
</HTML>