this last part! Senility is setting in. Anyway, change join project to
not send the email to the projleader when the user is new; let that
happen out of the verify page when the newuser does the verification.
Basically, duplicate some code to generate the email message.

XXX: I have not fixed up approveuser.php3 to check to make sure that
the user has been verified. Basically, for this to happen the proj
leader would have to generate the URL by hand, and thats not likely,
and not really a dangerous thing anyway. However, it is confusing.

node information web page.

information page. Got tired of having to past the them all by hand
between windows. Only admins can do this.

Also, add subpage menu stuff to make the page look nicer.

generating a warning in the startexp logfile.

happened (in the web page listing).

and a simulated node, things failed

bit set.  It appears that cvs doesn't notice just permission changes (?)

Add sorting by number of nodes reserved (PCs column). Right now this
is total number, so it includes widearea nodes, but I plan to split
these apart. Sorting by PCs required changing in the initial query
quite a bit. Also changed the final report to include all classes, and
convert into a prettier table.
Add a minor optimization; instead of querying the DB for the number of
node classes used by experiment (which at this moment means 107
queries), do one query and split into a little hash table of per exper
usage totals.

Big changes. Add idlecheck, sdisrunning and sddeploy to configure and the make files. Install sd* above into sbin dir. Rename sddeploy.pl and isrunning.pl.

Added default behavior so that when no pid/eid is given, it looks up
all the nodes that haven't reported in the last 2 hours and runs it
on those nodes.
Also added magic around ssh calls. Fork and set an alarm, if it doesn't come
back, declare the node unreachable and kill the child.
(This checkin is for checkpointing, I'm now going to add this to configure
so that it properly gets devel libdb.pm instead of hardcoded to the real one.)

detects that at least one of the nodes in the lan includes a remote
node. Of course, on links can include remote nodes, but thats okay.

1) Removed the ten iterations limit from main daemon loop I had set during
testing a while back (duh).  This was why slothd was mysteriously disappearing
after half a day.

2) Updated the makefile to produce static slothd binaries

3) Added a locking mechanism to avoid accidentally starting two slothd's
simulatneously.

Checks to make sure that all ports for an experiment are in the
correct switch state. If they are enabled, they should have
carrier.

Note that enough code is shared between checkports and portstats
that some of it could probably be moved to a library at this
point.

than rc.testbed.  Since rc.testbed calls cvsup, modifications to this file
do not take effect until the next reboot occurs.  This is why slothd was not
starting on many nodes.

an experiment fails to setup properly (we were leaving them running).

First, gives us a handy way to build all the tools, if there
is ever more than one.

Second, it's a workaround for a really annoying problem with
configure. Since there was nothing in the tools/ directory itself,
it wasn't getting created, so configure could not make
tools/pcapper (since the parent directory didn't exist.)

Section mentioning non-default daemons started by testbed scripts updated
with slothd info, and corrections were made to the healthd info.

request.

recommendation by Dave in email to testbed-ops).

(punting for today on indicating directions for non-symmetric attributes,
though both are listed.)

Now, due to changes in the parser, lans must have $'s before the name of each node.
(shashi says this is the proper ns syntax) Changed java code to do this.

Event system:

When compiled with -DEVENTSYS, can be made to wait for time to start
in an experiment before starting to count packets. Times are also
reported relative to experiment time start. Use the '-e' flag to
enable.

SUID support:

If compiled with -DDROPROOT, and it seems that pcapper was started
setuid root (euid == 0, and ruid != 0), drops root permissions after
opening BPF (or raw socket in Linux.) This allows it get permissions
to read packets, but still be killed by the user. This is particularly
useful with the testbed's program objects.

New command-line options:

-s: Print out packet counts to stdout, in addition to listening
        on a socket ('-f -' does the same thing, too)
-p: Count only payload sizes, not header sizes
-e: Wait for event system time to start in pid/eid
-z: Don't count zero-length packets in the packet counts (useful
        with '-p')

Also, now creates a GNUmakefile the _right_ way.

Refer http://www.isi.edu/nsnam/ns/doc/node125.html

* Cleanup! A lot of the structure derived from the early frame days,
  which had a noticable (and bad) effect on how I wrote the stuff.  I
  cleaned up most of that yuckyness.

* In process, optimize a little bit on the queries. The old code did
  about 9 queries just to write out the menu options, and then
  repeated most of those queries again in the page guts. I've
  consolidated the queries as much as possible (to 3) and cache all
  the results.

* Fix up problem with users who forget their passwords before
  verification. Basically, I fixed the more general problem of not
  being able to update your user info before verification/approval;
  users now get that menu option no matter their status.

* Fix up problem of users being able to access pages before
  verification (but after approval) by going around the menu options.
  The page level check (after the menu is drawn) now checks all
  conditions (password expired, unverified, unapproved, timedout, and
  also nologins()).

* Minor change in approveuser; do not show the new account to the
  project leader until the new user has verified his account.

* Change verification method, as reqwuested by Dave.  In addition to
  providing the key, also provide a web link to take the user straight
  to verification. I actually take them direct to the login page, and
  pass the key in as an argument. If the user is already logged in,
  bypass and go directly to the verify page (not the form page of
  course).  If the user is not logged in, let him log in, and then
  forward the key onward to the verify page. Basically, bypass the
  form all the time, and just do the verification.

* Minor change in showuser; Do not show pid/groups not approved in,
  and if the count is zero, do not draw the table headings.

database (iddata_clean), and a script to generate fake idle entries for
testing scripts on the minibed (idloadup.pl).

iddata_clean, by default, removes all idle entries older than 36 hours.
This can be changed by providing -m <maxage> (in seconds) to it.

idloadup.pl adds random idle data at time offsets from now, to 5 days
prior (1 sec granularity).  It adds anywhere from 1 to 10 entries per
PC to the node_idlestats page, and from 1 - 10 x # interfaces to
the iface_counters table.