course; its an optional argument.

Add group stuff; we get a group (csh, tsch) and a routine maps that
into a valid path to use in the pw commands.

the vnode on whose behalf they are operating. The library passes this
through to tmcd.

Move definition of the delay_mapping file in from liblocsetup so that
it is easily exportable withou another hoop.

Add configuration support for veth devices.

Change route and ifconfig generated script to do enable/disable
segments in the generated scripts so that per-jail configurations can
be added/removed easily by mkjail.

Add program agents configuration, with corresponding tmcd command to
return the list of program objects for a node (or jail).

Trafgens inside jails talk to the local elvind, not boss.

dotunnels, doroute, doiconfig all take an optional rtabid and pass
that through to libloc routines.

Add trivial support for getting the user shell from tmcd.

is supported:

- stated listens for TBCOMMAND events, and currently handles REBOOT,
  POWEROFF, POWERON, and POWERCYCLE events. It does everything except make
  the actual calls to node_reboot and power. And it accepts batches of
  nodes instead of just single ones.

- Timeouts were added to the db for these commands, with no timeout for
  the power ones (since the node can't hang during those), and a 15 second
  timeout from reboot until the SHUTDOWN state.

- If a rebootimes out, it tries it again, up to 3 times. If it gets to
  three times without working, it sends mail to tbops and turns the
  machine off instead of continuing to reboot it. Right now I haven't
  made it do node_reboot -f or power cycle on retries, but it easily
  could.

- Stuff to be done before they work: make node_reboot send an event
  instead of doing the work, and make a new script that has node_reboot's
  old guts. Note that this requires authentication in our events for these
  commands, and a way to make sure that the command that came in as an
  event was properly authenticated.

- For future growth and expansion, it is set up so it should be relatively
  easy to add other commands that do different things, even if they take
  arbitrary params that aren't nodes or lists of nodes.

obviously doesn't get used anywhere yet.

plus the IN and CNAME records for the locally allocated virtnodes:

  pcvm82-2				IN      A       172.16.82.2
  node3.jail3-2link-full.testbed          IN     CNAME   pcvm82-2

reboot a node, we never call power directly. Instead, exit with
a status of 2 - the parent process collects a list of nodes that
needed power cycling, and does them all in one call.

combination of lans and trivial links.

for a jail node, since that must run outside the jail.
Add logfile/pidfile arguments to the delay_agent. If staring for a
jail, talk to local elvind instead of boss elvind (use the proxy).

on all DHCP events of interest.

Remove jaildog, and use the common watchdog instead.

script both inside and outside the jail.

run with the user group set. Bug reported by Eric.

On linux, do it the old way (talk directly to boss) until I get those
images updated with new stuff.

Add pidfile argument to program-agent.
Add logfile argument to program-agent.
Move uid/gid flip into the program-agent so that it can do a proper
setgroups, instead of the silly way that perl does it.
Add argument so that agent talks to local elvind, instead of boss
elvind (proxy always runs now).

multiplexing of nodes.

inside jails.

routing tables, a jail can be a router quite nicely.

federation, which is not supported in the version we have source to.
Basically, we run an elvind on each node. The proxy on each node
subscribes to all events for that node from the boss elvind, and hands
them to the local elvind, Each client on the node subscribes to the
local elvind, and gets its events via the proxy. This should reduce
the number of connections to boss, and makes it possible to run agents
inside each virtual node without an FD explosion on boss.

Add commented out find -delete command to remove all mysql logs older
than 35 days.  I just run it by hand at the moment, but I'll turn it
on at some point.

update V3 nodes to V4 CDs, and the new image. By inserting an entry
into this table, the node will update its image the next time it
reboots and checks in for instructions. The actual instructions are
hardwired in the web still, but this allows Dave to schedule updates
as needed. Eventually, the instructions will be part of the DB state
as well, but this works.

started before the interval (so, all we see is a swapout).

Note, I'm not dealing with the creator/swapper uid thing yet. TODO.

more useful, by including the reasons and such.

Also add a similar email message when they change the reasons or timeouts.

Epoch listing. Maybe later if we need it (since it reaches back to the
dawn of Emulab, todays experiments are not likely to have a big
influence on the numbers).