both are in there now via ifdefs (bleh).  Link the scheduler against the
threaded version of pubsub and add some asserts to ensure that's the
case.

The program-agent on ops seems to work with the scheduler now.

to do with the swig wrapper, I think. Not sure though, and I have to
take off for a few hours.

I commented out the client side stuff in the event directory though since
I initially trying to get boss running on the new system.

Minor change to event.c and event.h

/usr/local/lib since pubsub will not be part of the testbed tree.

indexed by exptidx. I also got the last of the pid and pid,gid tables.

Rev 20 of the tarball has no new function, it is just slimmed down.
I replaced our large statically linked binaries with dynamically linked ones.
Also found and stripped a couple of other binaries.

The resulting tarball goes from 5.7MB to 0.9MB.

The Makefile changes are to incorporate the NOSTATIC=1 environment hack
to enable building the dynamic binaries above.

This causes program agents to become isolated and marginalized, in short,
unresponsive to the needs of Emulab.  It is now a Loyal Emulab Soldier,
attempting reconnects til the end of time if necessary.

I left in the "keep alive" (idle timeout) since it doesn't seem to be causing
any problems.

 * if we have to create it, make sure to re-stat so that following
   /uid/gid/mode checks are legit
 * change the own/group if either of own/group are wrong

variables on cluster and plab nodes.

NODECNET (new)
The fully-qualified (Emulab) name of the node this program agent is running on.
This name resolves to the IP address of the control network interface
of the node.

NODECNETIP (new)
The IP address of the control network interface.
This address should not be advertised to, or used by, applications
within an experiment as it will cause all traffic to flow over the control
network rather than the experimental network.

NODE
The unqualified name of the node this program agent is running on.
For nodes with experimental interfaces,
this name resolves to the IP address of an experimental interface on the node.
For nodes with more than one experimental interface,
there is no guarantee which one it will resolve to.
For nodes with no experimental interfaces,
the name will not resolve.

NODEIP
The IP address of the experiment network interface that NODE resolves to.
For nodes with no experimental interfaces, this variable will not be set.

Removed duplicate declaration of make_timestamp in event-sched.h (also
declared in util.h).

Change timestamp output of event-sched to something human readable.

Also add a small amount of debug output to "$ns report" to help me
track down why it is being called at seemingly random places.

Some of these are on rinky-dink scripts, but it just makes life easier to
be consistent.

of adding copyrights to them.

than 35 program agents on the same node.

Reported by "Randy Robertson" <rmrobert@isi.edu>.

Add "-archive <bool>" to $ns report which controls if "loghole
archive" is called.  Creating the archive zipfiles is redundant when
using the workbench.  It only serves to wastes space (and time when
committing then to the experiment archive).

Fix intermittent one-way loss test failure.  Let bind() choose the src port in rude; any constant port like 3001 may be already in use.

between when something is installed and when post-install runs. Short
of a global lock (which we probably need anyway someday), my solution
is this. In your makefiles, add these variables before the line that
has the include of $(TESTBED_SRCDIR)/GNUmakerules:

	SETUID_BIN_SCRIPTS   =
	SETUID_SBIN_SCRIPTS  =

I have added three new rules to GNUmakerules that look like this:

	$(addprefix $(SBINDIR)/, $(SETUID_SBIN_SCRIPTS)): $(SBINDIR)/%: %
		echo "Installing (setuid) $<"
		-mkdir -p $(INSTALL_SBINDIR)
		$(SUDO) $(INSTALL) -o root -m 4755 $< $@

Yep, your eyes ain't lying to you; use sudo to run the target so that
install does the right thing (which is that the old file is not
replaced until the new one has the proper attributes on it).

Note that post-install is still needed for the initial install, but
should no longer be needed for day to day installs since all that other
stuff post-install does is mkdir/chmod on directories.

Two-day boondoggle to support "/scratch", an optional large, shared filesystem
for users.  To do this, I needed to find all the instances where /proj is used
and behave accordingly.  The boondoggle part was the decision to gather up all
the hardwired instances of shared directory names ("/proj", "/users", etc.)
so that they are set in a common place (via unexposed configure variables).
This is a boondoggle because:

1. I didn't change the client-side scripts.  They need a different mechanism
   (e.g., tmcd) to get the info, configure is the wrong way.

2. Even if I had done #1 it is likely--no, certain--that something would
   fail if you tried to rename "/proj" to be "/mike".  These names are just
   too ingrained.

3. We may not even use "/scratch" as it turns out.

Note, I also didn't fix any of the .html documentation.  Anyway, it is done.
To maintain my illusion in the future you should:

1. Have perl scripts include "use libtestbed" and use the defined PROJROOT(),
   et.al. functions where possible.  If not possible, make sure they run
   through configure and use @PROJROOT_DIR@, etc.

2. Use the configure method for python, C, php and other languages.

3. There are perl (TBValidUserDir) and php (VALIDUSERPATH) functions which
   you should call to determine if an NS, template parameter, tarball or
   other file are in "an acceptable location."  Use these functions where
   possible.  They know about the optional "scratch" filesystem.  Note that
   the perl function is over-engineered to handles cases that don't occur
   in nature.

we will never be called if not.

reload and halt events send proper completion events. This is required
for stoprun and startrun to work correctly. On stoprun the logs are
not collected until the programs have stopped, and on startrun we do
not want to proceed until all the agents have reloaded their
environments.

to tevc to wait for the reset to complete:

	tevc -w -e testbed/TT now link0 reset
or
	tevc -w -e testbed/TT now __all_lans reset

where __all_lans in another internally created event group.

knows when the logfiles are actually rolled.

Event groups complicated things a bit. To make this work properly, we
no longer subscribe to the link-tracemon event, but instead use a
real event group, created by assign wrapper for all of the linktrace
agents. So, you can know do things like this:

	tevc -w -e testbed/TT now link0_tracemon snapshot
or
	tevc -w -e testbed/TT now __all_tracemon snapshot

where __all_tracemon is a group of all tracemon agents for all links and
lans. I plan to change loghole to use this.