GitLab

tbsend.c and tbrecv.c, which are trivial examples of how to send
and receive a sample event.

already a pid associated with the experiment (unless clearing it to
zero). This enforces the restriction that there should only be a
single event scheduler running for an experiment!

Daemon if it exists.

which agents are attached to which node, so that we can assign
portnumbers to them. Also add code to updating the DB with these
agents (virt_trafgens).

sim.tcl: Get rid of $pid_$eid_events (per experiment events table),
and replace with global eventlist table. Revisit this later, since it
was causing problems and we do not really have a problem right now.
Maybe later.

traffic.tcl: Add virt_trafgens DB table update code. Get rid of oskit
based traffic generators and replace with FreeBSD nodes, which will
boot up and check if they are traffic gen source. Add get_params call,
called by the event code im sim.tcl to get the current params for the
START event.

generator node.

matches the one in the checked-out source.

This now gets called as part of the 'boss-install' target, to guard
against installing software that is out-of-sync with the running
database. It is skipped if @prefix@ is not /usr/testbed, to avoid
getting in the way of development.

If you want to bypass this check, use the 'boss-install-force' target.
Use of this, however, is not recommended.

Also, now indicates differences, or lack thereof, with its exit value.
Returns 0 if there is no difference between the schemas, or 1 if there
is one.

rather than assuming a fixed size of 640x480.
Should provide more room in workarea for network designs.

events .

pedantic than either opera or IE, or more likely just stupid).

our web access checks are in php3, it's wrapped in a php3 wrapper
script. Access to it is controlled via the cvsweb column in the
users table.

cvsweb only gets installed on the main emulab site - that is, if
OURDOMAIN is defined to be emulab.net

cvsweb itself is originally from http://www.idaemons.org/~knu/cvsweb/

Minor fix; solves a potential security problem by ensuring backend will execute no code if called directly.

Note: I edited out the tables created by the event system. We should
probably have a script that does this for us.

event system.

included on the client side (no mysql setup).

cabling suggestions, as per Jay's request.

not being used on www.emulab.net

Got new visualization integrated...
Put .png files for icons in www/ (both src and build trees)
..those should probably be somewhere else eventually (at least in a subdir of www),
but they're happy there for now.

visualization stuff.

to reduce stray traffic, etc.