batch jobs will end! There were two problems; 1) The socket was
744, so mere users were not able to run tmcc. 2) libsetup was not
even using the proxy socket cause it was never looking for it.

the batch system see's them as always done. There is no reason to do
this from the node itself, since it would be really hard to have
either a jail or delay node without other nodes in the topology!

search box so that we can search for a user name.

protocol for external scripts. Now that Mike has been successfully
embarrased in front of everyone, I will document said protocol:

	$status < 0 - Fatal error. Email output to tbops.
	$status = 0 - Everything okay!
	$status > 0 - Expected error. Give results to user only.

Of course, only 4 scripts have been adapted to the new protocol, but
thats okay. I'm sure Mike will trip over them all eventually.

awaiting word from Kirk.

plus a lock field. The lock field was a simple "experiment locked, go away"
slot that is easy to use when you do not care about the actual state that
an experiment is in, just that it is in "transition" and should not be
messed with.

The other two state variables are "state" and "batchstate". The former
(state) is the original variable that Chris added, and was used by the tb*
scripts to make sure that the experiment was in the state each particular
script wanted them to be in. But over time (and with the addition of so
much wrapper goo around them), "state" has leaked out all over the place to
determine what operations on an experiment are allowed, and if/when it
should be displayed in various web pages. There are a set of transition
states in addition to the usual "active", "swapped", etc like "swapping"
that make testing state a pain in the butt.

I added the other state variable ("batchstate") when I did the batch
system, obviously! It was intended as a wrapper state to control access to
the batch queue, and to prevent batch experiments from being messed with
except when it was really okay (for example, its okay to terminate a
swapped out batch experiment, but not a swapped in batch experiment since
that would confuse the batch daemon). There are fewer of these states, plus
one additional state for "modifying" experiments.

So what I have done is change the system to use "batchstate" for all
experiments to control entry into the swap system, from the web interface,
from the command line, and from the batch daemon. The other state variable
still exists, and will be brutally pushed back under the surface until its
just a vague memory, used only by the original tb* scripts. This will
happen over time, and the "batchstate" variable will be renamed once I am
convinced that this was the right thing to do and that my changes actually
work as intended.

Only people who have bothered to read this far will know that I also added
the ability to cancel experiment swapin in progress. For that I am using
the "canceled" flag (ah, this one was named properly from the start!), and
I test that at various times in assign_wrapper and tbswap. A minor downside
right now is that a canceled swapin looks too much like a failed swapin,
and so tbops gets email about it. I'll fix that at some point (sometime
after the boss complains).

I also cleaned up various bits of code, replacing direct calls to exec
with calls to the recently improved SUEXEC interface. This removes
some cruft from each script that calls an external script.

Cleaned up modifyexp.ph3 quite a bit, reformatting and indenting.
Also fixed to not run the parser directly! This was very wrong; should
call nscheck instead. Changed to use "nobody" group instead of group
flux (made the same change in nscheck).

There is a script in the sql directory called newstates.pl. It needs
to be run to initialize the batchstate slot of the experiments table
for all existing experiments.

of nodes an OS is running on - this way, we don't count, for example,
nodes that a reloading.

one from my devel tree).

everything else goes to stdout. This will hopefully make things a bit
simpler by avoiding funny buffering issues for programs like
assign_wrapper that want to redirect assign's stdout.

rather than creating a new partition.

lot of sense.

thinks mere users are trying to set their swappable bit to off. Since
it wasn't displayed on the mere-user form, it isn't in the form data
sent back, so it looks like they're turning it off.

weeks)

desire for 'hosts-<type>', where <type> is the type of its child node.
This helps assign, because it can now limit the number of places to
try assigning the host, and it means that we can give the hosts this
feature, so that they don't get used for other purposes. For example,
we can give the IXP-hosting nodes the feature 'hosts-ixp-bv' with
weight 1, and they will never get used for anything but IXP hosting.

This means that the node_type_features (or just node_features) table
must now have hosts-<type> entires to work correctly.

put:
$node add-desire desire weight

This will end up in the virt_node_desires table. assign_wrapper now
puts the desires from this table into the top file.

multiple desires for each vnode.

In particular, this keeps the ixp host nodes from showing up.

Needs eyeballing & checking after installation.

into assign.

from my devel tree).

does the daemon.