(and so, has been renamed setVlansOnTrunk). Part of the work necessary
to get the stack-level setVlanOnTrunks function to accept multiple
VLANs in one call.

performance analysis or validation done yet.

First, we'll no longer have seperate sup releases for each revision,
so the supfiles use the release 'current'

Second, since we no longer have seperate sup releases, the prepare
scripts no longer need to remove checkouts files.

* Add ability to control timeout when invoking tmcc, and whether to
  fatally die if tmcc fails. Related change was to allow more options
  to be passed into tmcc by way of an additional options argument.

* Change to pubkey handling. tmcd now returns a list of pubkeys for
  each login. The entire list is written to the authkeys files, and
  the old is backed up (with mod time preserved).

* tmcd now returns a serial number for each use to indicate when
  user info has changed (via the web pages). Only users with updated
  serial numbers get modified (and new authkeys file created). This
  should vastly reduce the passwd/authkeys churning on the ron nodes,
  which periodically check for account updates. The little db file now
  records the serial number too.

* Change to os_usermod; Change the actual password string! Was not
  doing that before.

* Conditionalize all the tmcc.foo stuff that Shashi added; don't want
  any of this on remote nodes yet.

* Remove a bunch of printfs to reduce output clutter.

actually doing that on local nodes before. I guess I'm very ssh
centric (I never type passwords) but that appears not to be the case
for most people!

keys file.

well. We use a UDP packet to keep it lightweight. If it does not get
through, thats okay, obviously. The return value is just a yes/no flag
that says an update needs to run. Right now, thats just accounts.
This allows us to churn a little less on accounts.
Other cleanups.

when remote is set timeouts when trying to update accounts, and fail
more gracefully.

caused by hupping mountd are not getting propogated back until later
writes. Must do an fsync to catch the error. Too many fsyncs slows
down imagezip by a factor of three though, so I reorged things so that
we create the 1MB chunks all in memory, and then write out each one
out as finished. Much better; only a 10% slowdown.

to lose them!

Return the update_accounts flag so that the client knows to
update accounts. This flag is set in node_update for remote nodes.
Once the client picks up accounts, decrement the update_accounts flag.
This functions a simple barrier (up/down counter so that clients
do not miss).

mode.

started.) Instead of avoiding sending an event when we think the
node will be sending it, go back to always sending it. Nodes
sending the events on shutdown just isn't reliable enough. Instead,
we'll just make two REBOOT events in a row legal.

indicating when the image was last updated. This gets updated by
create_image .

The hope is that it will give us some idea of which revision of
our standard images custom images are based off of.

fixe's the config.status bug.

Fix broken calculation of hours since last swap request was sent. (had problems when the time was from yesterday.)

Add idle_ignore column to db. Makes idlecheck completely ignore it when looking for idle expts. Unswappable expts still get checked and possibly harassed if they go idle.

Fix up idle view better for slothd now that we trust it more. Add info about # of swap requests and last time of a swap request too. Took out lastlogins column for idle view, but the sanity check still happens.

swapin.

defaults for other fields.

subtract that out form the numbers obtained from the switch.  So, we
have a new option to 'zero' (store current values) of counters.  This
is intended to be used at experiment swapin, but can also be used by
experimenters whenever they want.

Along with this, the following new options:
-z    Zero out counts for selected counters, after printing
-q    Quiet: don't actually print counts - useful with -z
-c    Print absolute, rather than relative, counts

want to report switch activity since a certain time (say, experiment
swapin.)

and last_swap_req) track the count and last time a request was sent.

The counters all get reset by idlecheck every time it runs unless it
detects you as inactive. Then when you go to send a swap request, it
will show you the info about how many have been sent and when the last
one was, and will let you know if the swap request will also go to the
proj leader if you send it. When you send the request, the email
mentions how many reminders you've been sent already, and only gets
cc'd to proj head on the third message (or more). Then it updates the
count and the timestamp of the last request sent.

Fix cut/paste error in email... always said yes on returning user line even when it knew it was a new user. (The logic all worked right, it just printed the wrong thing in the email.

If the expt is activating, add a link to spewlogfile. Currently only works if you're the person who started the experiment, due to the ownership/permissions of the log file we create.

take more than one. This can increase efficiency, since, for example,
we now only have to lock the VLAN edit buffer once when tearing down
an experiment, instead of once per VLAN. There are still other
functions (setVlanOnTrunks comes to mind) that could benefit from this
treatment.

These optimization have been made only for Ciscos - minimal changes
necessary to keep Intel support working were made, but they will still
have the same old slow behavior.

if it is inside make-simulated.

For nsenodes, I ask for a pc850 if available for more CPU horsepower

create images from/for each node type. Use this in the newimageid
forms to present a shortened list of node types. Also, add a footnote
explaining typical usage.

create images from/for each node type. I'm gonna use this in the
newimage forms to control the list of node types.

appear to be working, so experiment setup is not working correctly
when nodes fail.