bgmon-running node to that of another node.

The samples with long RTT values are removed for possible lack of symmetric
one-way delays. The remaining samples with offset outliers are also removed
by the median filter.

 * auto-pelab.ns: add an event-group that runs 'update -t' on the nodes
   to update the tarballs/RPMs.  NOTE that you will need to modify your
   experiment and update your version of the NS file for this to work.

 * install-tarball: simple script to run tevc and trigger the tarball
   updates

 * start-experiment: '-p' option to monitor the real planetlab nodes
   instead of the emulated ones, -M/-S to set the arguments passed to
   the monitors/stubs, -m/-s to append to the current arguments passed
   to the monitors/stubs.

 * monitor/auto-monitor.sh: pass through the command line arguments

things like inter-write timings.

to somewhere other than stdout or netmond.

See:     #MARK_RELIABLE  sections

w/o it.

event a chance to get out.

Update the plab proxy to manage restoring the connection to the remote
elvind on ops itself (instead of leaving it up to elvin).

This whole program needs cleanup/refactoring attention.  Later.

It interacts badly with the JVM.

This means we can (and do) report the connect() BEFORE the handshake
is done, which helps keep the stub from starting far behind.

There is a new LocalPort message returned after the connect()
finishes.

Fixed a bug with accept()ed sockets.

results to stdout instead of to netmond.

the monitor and the stubs.  Otherwise the new ones were immediately
being killed off.  Some sort of event delivery issue?

on initial page load; mysqld has gone catatonic and we find out about
it many other ways, so lets not add more email to the flood.

which the delay node needs, gets fired.

Look at "SCHEDULER" attribute to get most everything.

Added silly little program to dump the set of subscriptions registered
on an elvind server.  Uses the "quench" feature to grab this set.  Note
that there is no way to just ask for everything, you have to specify the
subscription attribute you are interested in.  However, since the testbed
elvin library wrapper always adds certain fields, just asking for one of
these almost certainly gets you everything you are looking for.  The only
exception (missed items) would be custom subscriptions created directly
via the elvin library that do not include one of these common fields.  I
don't think such subscriptions are ever created in practice.

history data.

cloud (like make-lan)

is breaking, next time it happens.

bandwidth to something like 54000kbits (54mb) was really more like 55.3mb.
Now we just spit it out in bits (54000000) to be safe.

like node MAC addresses and whether linkdelays or veths are being used.