(if I am wrong on this, let me know, guys).

transition error when you click too fast after creating it. Instead of
looking at experiment state, use the logile slot of the experiments
table, and make sure its cleared/set properly in start/swap experiment
scripts.

Also added a spew option to the swap page so you can watch experiments
swap in/out.

be links.

as requested by Jay.

read. The impl (menu stuff) needs to be cleaned up for sure.

but simply entered into the DB record for the experiment until we know
what to do with them. Add to batchexp script arguments, since all that
stuff is done outside the web interface. Add a swapexp perl script to
swap an an experiment in/out form the command line. Add web links on
the Experiment Information page to do this from the web interface. A
bunch of locking changes. Previously expt_terminating in the
experiment record prevented multiple calls to terminate an experiment,
but now we have a more general locking problem with
start,swapin,swapout, and terminate, so change expt_terminating to
expt_locked (still a datetime field) and add locking to all of
startexp, swapexp, and endexp. Note that batch experiments cannot be
swapped yet because of locking issues still to be resolved. Minor
cleanup in tbreport to make email message look better.

experiment code. No longer uses another table. Rather, the experiment
record contains a couple of extra fields for the batch system. Also
combined some of the backend code (no longer a killbatch script).
Also added scriptable experiments; the batchexp program in the bin
directory can start an experiment from the command line, and in fact
is used from the web page for both batch experiments and immediate
experiments (-i option). All of the DB code that was in the web
interfaces was moved to batchexp.

of problems.

Change to startexp/endexp, which are almost scriptable now (can be
called directly in addition from the web page). Add front ends to
these for the web page (webstartexp and webendexp). These changes are
mostly support for batch mode.

termination, setup now exits immediately and sends email to the user
when the experiment is fully configured.

by the web server forks a child to do the actual work of calling tbend
and other stuff. The parent returns right away and the script ends.
When the experiment termination (child) ends, an email message is sent
to the user that issued the termination request. To prevent multiple
clicks, I added a DB field called expt_terminating that is a DATETIME
field.  If the field is set, the script fails and the user is told to
be more patient. I used a DATETIME field mostly for debugging purposes
so we can track and future problems.

option list, use a plain list instead. Simplify the DB queries now
that I'm a joining fool, and put in a proper confirmation step for
ending an experiment. Yippie.

who the user is instead of passing ?uid to every page all the way down.
Update login timeout with each useful operation (done in checklogin).
Put default user name in the login box when visiting the page.

webserver, as the uid of the experimentor. Not fully debugged yet
since the testbed has been kinda broken all day, but this needs to get
in if anyone else works on it.

of all that duplicated goo).
Clean up all the formerror code, calling standard FORMERROR() function.
Get rid of all the inline DB specific constants, moving them to dbdefs.php3
include file.

This just adds and deletes the database field entries (experiments table)
so that other things will work correctly.

EIDs no longer concatenate the PID into the string, but instead there
are independent PID/EID fields to make experiments unique. Also, there
were changes to the tb* scripts.