Add wrapper script around dhcpd to restart it if it dies; whenever dhcpd dies, the testbed becomes unusable.

distributions; includes lock/delete statements to clear out existing
tables before filling them again.

Add db-fill-dist target to sql/GNUmakefile to use this new option.

Add target to utah/Makefile to call into the sql makefile and run the
db-fill-dist target. Be careful not to check this version in locally
of course.

to date if the check fails.

currently used.

node_types:isphantom which I added in 1.256 since I decided not to use
it; just use isdynamic instead. Add an isjailed slot to node_types
rather then hardwiring that fact to "pcvm" node type.

in table_regex.

touching a standard script

loopback interface (yeah, Linux will really do that...)

Also eliminate the non-REBOOT/BOUND/RENEW case up front to avoid excess
checking.

standard scripts.  The current FreeBSD 5 image uses this.

case that a delay (or all delays) are removed in a swapmod.

and php wrapper.

Add control- or shift-left-mouse for rotate as an alternative to middle-mouse to the usage message image.

linktest running at once (not a likely situation but ...). Also give
the window a meaningful title so that the browser does not stick in
the URL path.

buffering so that it will start to display output line by line.
1024 for Firefox, probably the same for Netscape. I hear that IE is
256 bytes.

so that the process ID is tracked in the DB and so that the user can
stop a linktest in progress from the web interface, even if its
started directly from experiment swapin.

* Changed the linktest web page to allow for killing a running
  linktest when called from the showexp page. Puts up a simple Click
  form, whose action is to call "linktest_control -k" which does the
  dirty work.

* Implement a simple frameset when running linktest. I did this cause
  it was something new and besides, it was more fun then trying to
  reverse engineer the modelnet model file. Anyway, when linktest is
  started, put up a new window that has a two window frameset. The
  right hand window is just the spew output from linktest as it runs
  (although with buffering not much turns up at first). The left side
  window has a single click box to stop the running linktest, whose
  action is to call linktest_control -k as above. By the magic of
  javascript, when the linktest finishes, the stop button is removed
  and replaced with a "Linktest Finished" message. So exciting.

in the DB, change that to Stop Linktest instead.

* The linktest daemon (the one that runs on the nodes) no longer talks
  to boss directly, but instead contacts the local elvind; rc.linktest
  is changed to reflect that.

* A bunch of signal handler changes to run_linktest.pl; do not rely on
  events to stop linktest when it is running on boss; when the user
  kills a running linktest make sure all the processes are killed
  explicitly.

* New wrapper script (linktest_control) for use on boss, specifically
  when being called from the web interface. This script handles the DB
  part (getting linktest_level and linktest_pid), making sure that
  only one linktest is running at a time (on boss) and reseting the
  pid in the DB as needed. The -k option kills a running linktest, and
  is invoked from the web interface when the user wants to kill one in
  progress. This gets the pid from the DB and sends it a TERM signal,
  which sends a TERM to the run_linktest.pl script, which sends a TERM
  to the ltevent helper app.

  Note that this wrapper is also suitable for the XMLRPC interface,
  although I have not added it there yet.

Minor additions: a hypview wrapper script to set up local shared lib loading; control- or shift-left-mouse for rotate as an alternative to middle-mouse; glob expression to fan-out top-level nodes in getExperiment.

* Do not have linktest daemon connect to boss; have it connect to
  local node elvind like all other local agents. Remove the event
  generation code (linktest was sending a KILL event to all other
  linktest programs), and replace with a system() call to tevc, which
  sends the event through the scheduler and exits; this will avoid a
  zillion tcp connctions to boss from the linktest daemon.

* A couple of process group changes to linktest daemon; the daemon
  appeared to be killing itself off.

* Fix to run_linktest.pl; It was just hanging after it completed,
  cause its child ltevent process was still running. Changed to record
  child pid, and kill/close ltevent child before exiting.

from libsetup (ISDELAYNODE()).