print(STDERR"Usage: node_reboot [-d] [-f] [-w] [-k] node [node ...]\n"." node_reboot [-d] [-f] [-w] [-k] -e pid,eid\n"."Use the -d option to turn on debugging\n"."Use the -e option to reboot all the nodes in an experiment\n"."Use the -w option to to wait for nodes is come back up\n"."Use the -k option to power cycle nodes in PXEWAIT mode\n".

## If this is a firewalled experiment, don't reboot the firewall.# If you want to reboot the firewall, you have to do it individually.## Two reasons. One is that the firewall is not conceptually part of# the experiment and the user should not "be aware" of it. This# is a pretty lame reason because pretty much everywhere else, the# firewall IS part of the experiment. That leads to reason number# two: rebooting the firewall causes all other nodes in the experiment# to become disconnected until the firewall reboots. For some machines,# that are also rebooting as you recall, not getting PXE info for a# significant amount of time causes them to fail to the next boot.# For some machines this might mean halting ("Strike any key to continue"),# as there is no other boot possibility. This means ya gotta come back# later and reboot all those nodes again.#my$firewall="";