landing page knows what to do.

their PIs, but not too often.

gets really really big.

Add a "last activity" timestamp indicating the last time the user was
known to interact with Emulab by logging into the portal, logging into
a node or performing some other activity that resulted in their home
directory being exported (this latter may be dumb, not sure yet).
This should provide additional information about whether a user is really
using Emulab or is just someone who was in a project once and maybe
graduated and moved on.

Added a canonical "location" string to identify the user's home city.
This is the "formatted name" returned by the Google Maps API call
(with commas replaced by semicolons to prevent issues with CSV export
of the data). This field is intended to be a canonical rendition of the
city/state/country info the user enters.

That script was also modified to include users that are "frozen" or
"archived" by default. Unfortunately, just because they are in those
states now, does not mean they were during the desired time range.
Emulab keeps no indication of when they might have changed state.

The new -U option can be used to elide records for users that we have
determined were not active during the time range (i.e., their "last
activity" timestamp above is before the indicated start time.

Check each individual counter for wrap before aggregating counters.

Use absolute mode of portstats (-c) to avoid counter resets at experiment
boundaries and at the whim of the experimenter.

images are in the image server.

locked down and didn't need to be).

If the app fails to launch after 10 tries, give up.

Refined the hack to detect the case where we wind up in progmode()
on a restart before the old child has completely disappeared.
Somewhere we still have a race that leaves behind capture zombies.
The party really starts when we run out of processes!

error.

sql/database-create.sql had the correct schema all along.

Note that the shared-node-listener should be doing this, but this
is easier.

a single choice (as per meeting last week).

what I learned doing the bridges.

clicking on their buttons. Also some fixes to hopefully prevent node
context menus from getting left behind (cause Jacks is not passing out
the event I need).

possible for people of only average intelligence, to create pretty graphs.

for all running experiments so that the web interface is updated. Normally
the event stream tells us about changes, but having some problems with
that, so put this in place until I get that figured out.

Hide announcements when seen_count exceeds max_seen or when max_seen is zero.