GitLab

viewing the log.

fails. In batch mode, the daemon takes care of this, but in immediate mode
the parent script has exited, so it has to be done here.

Add 'update users set admin=1 where uid='flest';' to the dumped db so that flest is set as admin for its runs. Gives it magical powers to clear out all the expts. We may want to someday change this to be UID instead of 'flest', so that whoever is running it becomes admin. But for now, I think everyone who runs the test suite already is an admin.

done a couple of weeks ago).

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.

Now back to its old behavior, where frisbee reloads are handled no differently
than other reloads, because this difference is now taken care of in the
reload_daemon.

Note that the '-w' flag has been removed. This is due to an error that perl
reports on line 123, which, as far as I can tell, is not real. The code works
fine, anyway.

reloads to finish.

commit.

reserved to get its load info.

Did this with a little DB table that lists any aux machines that
groups need to be built on.

group, you need a -G "" argument? Had to read the source code to learn
that.

the OSKit.

testbed boot process and the freebsd pxeboot/MFS kernel. I'm hoping
this will be useful enough for users to load their own disk images,
but we shall see. Usage is simple:

	/usr/testbed/bin/node_admin on|off pcXXX

The "on" state boots the MFS, and the "off" states sets it back to
normal.

mounts).

eid in the portmap table.

reboot.

VLANS problem and ensures that the node state is cleared by nfree.

we don't have a root user in the DB. Perhaps this is bad?

Also made the 'forbidden character' message somewhat more helpful.

Changed request behavior to try to fill the most full of incomplete buffers, rather than a random one.
Also changed MB request to be a bit cleverer (tries to find contiguous received blocks and grow around those)
Changes resulted in less "bimodal" behavior and lower overall average runtime.