switches, in case we only have wide area nodes. Of course, snmpit
won't _do_ anything, but it shouldn't be an error to run it.

(Client was sending NULLs, which were echoed back

by the server as literally a '^' and a '@'),

Quick fixup of some of the documentation linking while adding info about idleness/swapping out. Added a faq question and a node usage policies document in swapping.html

different. Also for protocol 1 in sshtb. Some error condition
fixes in mkacct as well; the error log was not getting email properly,
and I'm not really sure why.

Also changed PID file from /var/run/slothd to /var/run/slothd.pid

/var/run/slothd to /var/run/slothd.pid

Lets hope I've finally put it in the right place..

links that do not need to get created in the ops install target.

sshtb also checks for unified control nodes, and if the destination
host is one of them, just runs the command, rather than invoking it
remotely via ssh.

when loading the default image.

initiated model for updating remote nodes.

way, this time.

project on a new emulab installation. It puts only the minimum
amount of information in the database, to avoid bitrot, then calls
the mk* scripts. This should help bootstrapping signficantly.

respect the adminoff flag.

This call appears to always reselect the DB, which might be a problem
when the DB is busy.

the actual query.

since we are saving just a single slice, and 0 is actually the MBR (by
local convention).

reporting in isalive status, and since we are returning a "need to
update" flag in the message, and since we are now initiating widearea
account updates by setting the flag for each node, and since tmcd
decrements that flag when the node picks up accounts, it is a simple
matter to do update for remote nodes! Simply, bump the flag in this
script, and then wait a little while to see whose flag does not change
back! Report those in the email message. Works very slick.

This mechanism is going to be generalized some to handle other kinds
of updates. Either via the isalive return value, or via a specialized
TMCD call to return the list of things that need to be updated. The
next most needed update mechanism we need is for the testbed software,
followed closely by user software.

doesn't change anything, but could be a mild information leak.

when there is only a single control node, that acts as both boss and
ops.

time in between retries.  This should help out when we have dozens
of experiments swapping in and out at once.

nodes.
Add handler for remote nodes, which now report keepalive once a
minute. Simply look at the timestamp and change status from up to
down if it has not responded in more than 90 seconds. This is kinda
crude, and mostly for the benefit of the web page. The wan solver
will use the timestamps directly.

(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.