of virt_tables so that it is saved and restored like the rest of
the virtual state.

optional when using tevc (dynamic events). So:

	tevc -e testbed/progagents now prog0 start

will simply rerun whatever the last command was.

its going to get replaced at some point by a busy state. The swap
scripts properly set the next state before unlocking the experiments
table, which possibly leaves some small races as experiments
transition through states (which happens with the table unlocked,
cause I used to have this really handy variable called expt_locked,
which no one really likes anymore).

We either have to use more table locking, fix up expt_locked, or punt
and say it won't happen more than once in a few thousand operations!

instead of testbed-ops. Either way, Mike gets to see it.

state machine (state). All of the stuff that was previously handled by
using batchstate is now embedded into the one state machine. Of
course, these mostly overlapped, so its not that much of a change,
except that we also redid the machine, adding more states (for
example, modify phases are now explicit. To get a picture of the
actual state machine, on boss:

		stategraph -o newstates EXPTSTATE
		gv newstates.ps

Things to note:

* The "batchstate" slot of the experiments table is now used solely to
  provide a lock for batch daemon. A secondary change will be to
  change the slot name to something more appropriate, but it can
  happen anytime after this new stuff is installed.

* I have left expt_locked for now, but another later change will be to remove
  expt_locked, and change it to active_busy or some such new state name in
  the state machine. I have removed most uses of expt_locked, except those
  that were necessary until there is a new state to replace it.

* These new changes are an implementation of the new state machine,
  but I have not done anything fancy. Most of the code is the same as
  it was before.

* I suspect that there are races with the batch daemon now, but they
  are going to be rare, and the end result is probably that a
  cancelation is delayed a little bit.

* Add slots to users table to track number of failures in the last N
  seconds. If a threshold is passed (currently 4 failures in the last
  minute), the web login is disabled. Note that I do not disable the
  ops shell login at this time. Aging is passive; the values are cleared
  when login is successful, or when more then one minute has passed
  since the last failure. In other words, a burst of failures will
  disable the login, but failures over time are okay.

* Add login_failures table to do exactly the same as above, except it
  is on an IP basis (REMOTE_ADDR in the server). Currently the
  threshold is 8 failures in the last two minutes, at which time all
  logins from that IP are disabled.

In both cases email is sent to tbops (and the user).

The constants are defined at the top of www/tbauth.in, rather then as
site variables, to avoid pounding the DB when an attack is being
launched.

To clear a user freeze, go to the user profile page and use the
"toggle" near the bottom.

To clear an IP freeze: delete from login_failures were IP='1.1.1.1'

for tracking login attacks.

enthusiasm of those who want to replace expensive commercial solutions
(and so I don't have to tell people over and over...)

Currently, this only means defining a signature file and creating a
utility to make them and check them against a disk.  The signature file
is not used by frisbee/imageunzip yet.

object coz it is currently disallowed.

the compiler on cash happy.

testsuite, which doesn't have a webserver assiocated with it. This
will also allow the target to work before apache is up and running.

Fix a bug with $LOGFACIL .

connect a vnode to itself):

Move up the point at which we consider a vnode to be assigned - we
want to do this before we look for link resolutions, or the 'other
end' of a loopback link appears to be unassigned, which is not true.

Add a mecahism to watch out for scoring lookpback links twice. The
edge iterator for an undirected graph sees each vlink twice (there
are two 'out' edges from the vnode). So, we have to avoid scoring it
the second time.

Note that we still only allow loopback links if they are 'trivial_ok'.

tree.

parser:

* Change xmlconvert to use XML::Parser instead of the ad-hoc stuff I
  wrote. This was easier then trying to deal with multiline fields or
  all the special chars. XML::Parser does all that for me. Also make
  sure all fields are either properly quoted (with DBQuoteMeta) or
  regex'ed before we stick them into the DB. For the future, we need
  to add table/slot specific regular expressions.

* Also add Shashi's fixes to the parser; properly escape XML special
  characters, as well as cleanup of my original spitxml code.

no need to go to all this trouble; just create the tables.

them - the old method was relying on them coming out of the database
in the same order, which may not be the case.

cannot have a pkg-comment file.

version of the schema.

'perl foo.pl'

for key upload). Add more regexes and addslashes().

Various things that need to go into new sites' databases, but don't really fit
into database-fill.sql, which is auto-generated. Also, unlike the contents of
database-fill.sql, inserting these is not idempotent, since a site may have
changed them for some reason.

for key upload). Also fix parsing code for version 7 SFS keys.