GitLab

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.

* 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.

currently available to only people with stud=1 status in the DB.

* www/tbauth.php3: Add a STUDLY() function to check that bit.

* www/linktest.php3: New page to run linktest on the fly. The level
  defaults to the current level in the experiments table, but you can
  override that via the form on the page.

* www/showexp.php3: Add link to aforementioned page. STUDLY() only.

* www/beginexp_form.php3: Add an option (selection) to set the linktest
  level for create/swapin. Defaults to 0 (no linktest). STUDLY() only.

* www/editexp.php3: Add an option to edit the default linktest level
  for an experiment. STUDLY() only.

* tbsetup/batchexp.in and tbsetup/swapexp.in: Add code to optionally run
  the linktest, sending email if it fails (exists with non-zero status).
  Failure does not affect the swapin.