current functionality).

is addressed in tmcc.c

socket files does not exists (connect returns ENOENT) retry until it
appears. The caller is responsible for timeout (via -t option) just as
for the tcp case.

in the timestamps, and seeing what was taking so much time.

* Increase the overlap from two to four seconds (have vnodesetup exit
  earlier) so that the next jail can start sooner. Using getrusage it
  seemed pretty clear that there were plenty of cycles available to
  start the next jail going a little earlier. Instead of looking for
  the watchdog pid file to appear, I touch (in mkjail) a specific file
  in the jail directory , and have vnodesetup look for that file
  instead of the pid.

* Cut back the number of inodes in the filesystem! Sheesh, we ere
  creating 137,000 inodes for a 50MB vnode filesystem. Takes 1
  second to do that. Reduced to 30,000 and the time when to .1
  seconds. Could probably go even lower.

* Add -p option to fsck when restoring a jail from an existing
  filesystem. No need to force check the filesystem if its clean.

* Instead of running MAKDEV inside each jail filesystem (which was
  also taking .8 seconds to do), do it just once and stash a copy in
  /var/emulab/jails. Each jail does a "hier cp" of that master copy
  into the jail filesystem. Reduced the time to .05 seconds.

So, for the results:

Original time to boot a jail: 8.2 seconds, with the last two seconds
overlapped with the next one.

Original time to reinstate a jail after halting it (filesystem left
behind): 6.5 seconds, with the last 1.5 seconds overlapped with the next
one.

Original time to boot 16 jails on a pc850: 2 minutes and 12 seconds.

---------------------------------------------------------------------------

New time to boot a jail: 6.2 seconds, with the last 4 seconds overlapped
with the next one.

New time to reinstate a jail after halting it: 6 seconds, with the last 4
seconds overlapped with the next onw.

New time to boot 16 jails on a pc850: 88 seconds. Does this number ring any
bells? :-)

tbsetup/libtestbed.pm.in which we use on boss. I have modified these
routines in two ways (which need to be merged back into original
version at some point).

* import/require Time::HiRes module (/usr/ports/devel/p5-Time-HiRes)
  to get higher resolution gettimeofday() function that reports
  microseconds and seconds. Change the output routine to append the
  microseconds to the original HH:MM:SS timestamps that get printed.

* When turning timestamps on dynamically with TBDebugTimeStampsOn(),
  set an environment variable, and read that in so children also know
  to turn them on.

routing is not requested in the ns file.

(was "actually appeared" order).

late.  So wait 5 seconds and try again if the first tmcc call fails.

XXX this is a hack that should be replaced!

hardwiring it in this script.

do physical nodes) cause I figured that indicated a fatal error and no
point trying. But, it appears that jail setup is a bit flaky, and so I
will retry ones that failed, once more. Note that I look at the cancel
flag before doing the retry to avoid more pointles waiting!

I have not actually tested this path through the code; just verified
that the main path still functions okay!

experiment cause of failure!

get them from veth_interfaces, but not bothering.

direction of an emulated link.

pc3000 nodes using a special MFS.

use the new type with vnodes.

table for the appropriate pcvm types.

the tail file of course. Called from TBdbfork() in libdb, EventFork
resets the event handle so that the child does a reconnect. Note that
I do not disconnect in the child since I have no idea what that is
going to do to the parents connection to the elvind, as Elvin makes no
mention of what to do in the presence of a process that forks after
connecting to the event server. At the least, this avoids a bunch of
warnings and errors from vnodesetup!

<a href="http://www.ee.technion.ac.il/people/idish/Abstracts/Drum.html">
"Exposing and Eliminating Vulnerabilities to Denial of Service Attacks
in Secure Gossip-Based Multicast."</a> To appear in the
<cite>International Conference on Dependable Systems and Networks
(DSN 2004)</cite>, Florence, Italy, June-July 2004.

the link agent). You can now do this:

	link_config -s nodew1 testbed three-wireless lan0 ENABLE=yes

to bring a link up (or down; ENABLE=no). This just gets passed along
in the event arguments. Basically an alias for "tevc now lan0 UP/DOWN"
to make things a little easier. At present, wireless lans are brought
up/down with ifconfig since "txpower off" does not work properly.

I suppose I should add the equivalent changes to delay_config ...

was giving me multiple rows for nodes that have multiple interfaces in
use!