GitLab

Most programs already use that library; getting the stragglers before
I whack the library for mysql 5.X

and report the numbers without passing judgement on the results.

This way, the linktest instances can know who will be running linktest
and who will not and thus we can run on a subset of nodes.

there is a query (by Mike I think) that has this form:

          SELECT * FROM t1, t2 JOIN t3 ON  ...

Prior to 5.X, the comma operator had the same precedence as join, and
so it was evaluated left to right. Well, now comma is lower then join
and this query breaks cause the right side is evaluated before the
left side. The solution is simply:

          SELECT * FROM (t1, t2) JOIN t3 ON  ...

but as the manual points out, why not just use:

          SELECT * FROM t1 JOIN t2 JOIN t3 ON ...

and avoid precedence issues.

are now reserved words mysql 5.X. Skip to the next entry ...

5.0 client side is very picky about this.

5.0 client side is very picky about this.

Move Univ of Newcastle nodes to Europe class.  Oops!  These nodes actually
route over commodity Inet, which is what threw me off.

now and the -FUTURE kernel delay-agent has too many problems.

Set the magic variable in auto-pelab.ns and swapin your experiment.
Logs will wind up in /proj/blahblah/exp/blahblah/logs/<node>/<name>.tcpdump
after you run stop-experiment.

I did this with the program agent and duct tape.  If it turns out that
you can already do this with the link tracing framework, then someone in
Oregon is going to whomp me upside the head with a clue-stick and he'll
never let me forget...at least til he forgets in a day or two.

Fixed bug where a single packet in a quantum caused an infinite loop. Fixed a bug where only socket buffer size updated in a quanum caused an infinite loop. Outstanding issue: Odd emulab side latency. Way too low.

Added ping error handling: timeout, ttl exceeded, and unknown.
 Values returned to ops are negative numbers. The meanings of these
 is listed in the top section of bgmon.pl
Note, that these changes have not been tested but were not complex.
testing is a definite TODO.

IP and not the real plab node IP.

Minor bugfix - quote the "NULL" strings.

Commit the option I added to runbgmon/bgmon.pl that allows you to specify
which port iperf is to use (-i <port>).  Also fix a minor issue with latency
and bandwidth period option parsing.

of the planet-* links.

know what is actually being reported.

Look for the XXX in get_plabinfo to see where it needs to be beefed
up.

Added support for the new buffer-exhaustion method of bandwidth measurement. It appears to do the right thing, but I still need to test it using tg.

instructed via stdin to change its rate of sending and blocksize... and
can also be prescripted.  Unfortunately, I didn't get time to finish the
server...

Added a capped pending buffer which retains write and timing information. Minor reporting fixes. When I checked out start-experiment, it said that there was an RCS version and merged the changes into my version. Therefore checking in this version should be correct. Mike should doublecheck.

corresponding planet-* nodes.

One catch: I only did the backend, I didn't do the part that actually
looks up the plab nodes in the DB.  Once get_plabinfo() is filled in
with a real body, this will work!

in some cases.

Add list of categorized plab nodes.  Note that this list only contains nodes
that were known to be available as of _today_.  I'll need to go back and
add the missing down/unavilable nodes in order for it to be complete.

Changes to bgmon and friends to allow specification of an alternate experiment
to listen/send with (expt event field).  This defaults to "__none".  I also
put in options for specifying bandwidth and latency periods, and generally
fixed up option parsing.

The runbgmon script has also been changed to autodetect the pid/eid and pass
this to bgmon.  You can override this with the "-e" switch.