do!

The original operation was to save up every log file forever in the
work directory, and copy that out to both the user directory and the
info directory (long term archive). When I cleaned /proj on ops
yesterday of all this old cruft, I recoved 17GB of disk space. Yow!

So, the new operation is:

* Only files that end in .log are copied to the user directory. No
  longer copying out .top, .ptop, and a couple of other logs; 99% of
  users never look at these things. We still have them available to us
  though, on boss.

* At the beginning of each swap operation, clean out the work
  directory of all the old log files. These are named a variety of
  ways, so I use some pattern patches to do this.

* Jigger the names a little so that we do not name things in the form
  "$$.log", to avoid copying out different named files to the user
  directory each time; instead link the .log file to the real output
  file so that it gets overwritten each time, while still getting the
  per-swap files for long term storage.

reset. I've done this with an event group cause otherwise I was going
to get sucked into the event system and spit out the other end. You can
reset the delays in your experiment either from the ns file:

	$ns at 100 "$ns reset-lans"

or from the command line:

	tevc -e foo/bar now all_lans reset

and yes, "all_lans" is a magic token.

It would be nice to support per-link or lan reset, but that is going
to require reorganizing the delay start up scripts on the delay nodes,
since right now a single delay agent operates for muliple links and lans.

Make a version of the example which shows an unroutable control network.

Standardized way in which domain names for other emulab are given

Re-formatted poorly formatted entries

Re-order to put higher-impact emulabs first

Changed the dependency declarations and their associated function declarations to reflect a previous unstated assumption: Functions called on dependencies do not change those dependencies. Now everything is declared const and that has been propagated throughout the system.

PacketSensor

rather than StateSensor's saturated() check. This makes it behave more
like we had discussed in meetings - it now looks more directly for
packet loss.

losses. The advatage of doing it here is that we don't need to
re-create all of the checks a real TCP stack has to do - we just look
at what it decided. The downside, though, is that we don't find out
about loss until the retransmit happens, which could be a little while
later.

Also add checks for duplicate and old acks.

Convert to using Jon's new logging flags for low and medium detail
logging information.

* Add XMLRPC interface for template swapin,stoprun,startrun,swapout and
  add the appropriate wrappers to the script_wrapper on ops.

* Allow parameter descriptions in NS files. This is probably not in its
  final form since its a bit confusing as to what has priority; something
  in the NS file or a metadata item. Anyway, you can do this in your NS
  file:

	$ns define-template-parameter GUID "0/0" "The GUID to be analyzed"

  The rules are currently that the NS file description has priority and
  is copied to child templates, unless the user has modified a description
  via the web interface, in which case the NS file description is ignored.
  I know, sounds awful, but for the most part people are going to use the
  NS file anyway.

* Add "clear" option when starting a new experiment run; the per
  experiment DB at the logholes are cleared. Note that this is *not* the
  default behaviour; you have to either check the checkbox on the web form
  or use the -c option to the script wrapper, or clear=yes if talking
  directly to the XMLRPC server.

* Fix up how email is generated for template_swapin and template_create,
  so that Kevin can debug tblog/tbreport stuff, but also so that we maintain
  mail logs as before. I have made some improvements to libaudit so as to
  centralize the mail goo, and avoid duplicating all that stuff.

* Minor fixes to the program agent so that the new environment strings are
  sent before the program agent exits and reloads them!

* Other minor little things.

Reverted changes to time format. Added a 'SENSOR_DETAIL' and 'SENSOR_COMPLETE" logging options. 'SENSOR' should now be used for high level information, 'SENSOR_DETAIL' should be used for medium level information, and 'SENSOR_COMPLETE' should be used for low-level information. If SENSOR_DETAIL logging is turned on, then SENSOR logging is also turned on. If SENSOR_COMPLETE logging is turned on, then SENSOR_DETAIL and SENSOR loggin is also turned on. All three of these levels use the 'SENSOR' prefix when outputting logging lines.

detaching from the parent.

Also improve the logonly mode by adding a nodelete option, to retain
the logfile after the email is sent.

Minor improvements to the interface.

next sync (similar to how it works with the archive directive).

Streamlined logging so that only two fprintf statements are necessary. One for the prefix and one for the variable argument body. This is down from the 5 it was earlier. Also changed the format of timestamps to me more useful. Timestamps are now in a secs:millis format rather than a floating point number. And secs is seconds since the beginning of the run (rounded to the nearest second) rather than seconds since epoch.

rather than signed ones.

Changed order of input file to <src> <dst> <bw> <delay> <loss> to bring it in line with Kevin's request.

Changed logCleanup() so that it uses a switch statement rather than a series of if statements. Now if there are more than one flags selected, only the first one encountered will be printed as a prefix. This should make things run faster.

up the max write size to 8k (we still write the correct number of
bytes if the app makes a write bigger than this, we just do it in
a couple calls to write().)

Added an extra field as a placeholder for loss in the initial-conditions format as per Mike's request.

Use '-' for stdout, e.g.:
	init-elabnodes.pl -o - tbres planetmikelab >> foo

Added initial conditions handling to monitor/stub. This should also solve the what does throughput mean when the connection is delay-dominated? problem. Now there are two kinds of bandwidth measurements that the magent can send back to the monitor. There is a throughput measurement which is tentative and which is applied only if it is greater than the last measurement. And there is a bandwidth measurement that is authoritative and is applied regardless.

which, oddly enough, ensures that update does not return immediately.

with a simple malloc()ed buffer, which cut about 20% off our CPU
usage.

Note, this could probably even be put into a statically-sized
structrure, but Jon would have to verify this.

out to burn too much CPU.

and gprof.out go to a place loghole will find them.

Change where the TMCCVNODEID environment variable gets setup.  Since
vnodesetup is the highest common execution point in the chain (for either
initial vserver startup, or subsequent reboot), this is the place to put it.
The previous stages don't need it, but just putting it in rc.vinit excludes
it from getting set during initial setup and boot.

Change types of latitude and longitude columns in widearea_nodeinfo to
float (instead of float(6,5)) to fix problem with values getting adjusted
improperly during insert.  Apparently the definition of the float(n,m)
type is non-standard, and has changed since sql 3.x.  Regular float
columns will do fine here.

Add patch to modify Mysql.pm to allow setting the "InactiveDestroy" in
the underlying DB handle.  Also avoid disconnecting the file handle
explistly on DESTROY as that will be taken care of in the DESTROY
method for the the DB handle.

Override perl version of fork() to set InactiveDestroy in all open
database handles in the child so that it won't send a disconnect when
the handle is destroyed as this will also close the database handle
for the parent.  It will also call tblog_new_child_process in the
child process to properly inform tblog of the new process. This will
be a NoOp if the libtblog module is not loaded.