tmcd listens on port 7777 for both UDP and TCP.
        UDP replies are buffered and sent as a single (up to 8k) packet.

        tmcc can be compiled to make UDP queries as well as TCP
        Not defined by default, used for debugging

Cleaned up some lint.

Change to startexp/endexp, which are almost scriptable now (can be
called directly in addition from the web page). Add front ends to
these for the web page (webstartexp and webendexp). These changes are
mostly support for batch mode.

with testbed-ops.

user/none trust and approved/unapproved.
Allow admin types to terminate any experiment.
Add trust/approval status in user list in project page.

fixing bugs.

   font. Don't like? Set you font prefs in netscape.
2) Add link to Flux Utah Network Testbed page along bottom of all the
   pages.
3) For the above, put in <base target=_top> tag just prior to the row
   of links along the bottom so that when you leave the testbed pages,
   you get a full window view instead of a framed view.

serial line shows up always.  Also reduced name length so we no longer
beet the 32 char limit.

handle_ip - Bug fix.

Also create a .forward file from the user email address so that email
gets forwarded off instead of sitting around.

See www/tutorial/shark_howto.html.

better there so I'm removing this copy.

their name.  Raised the limit to 1024.

you pick up the changes in format from the default-defs.php3.

Anyway, I wasted over an hour trying to figure out why I couldn't get the
documents in right hand frame to go through the non-secure server. Turns
out that http://www.emulab.net and https://www.emulab.net are techically
different servers, and browsers have a "security" feature to prevent
"hijacked frames" whatever the hell that is. If the link to be placed in
the target frame is on a different server, it will open a new window
instead. So, by starting a http://www.emulab.net/welcome.html in the right
side, and then trying to put https://www.emulab.net/newproject.php3 in it,
a new window pops up.

Sigh. So, until I figure out a suitable work around, the Welcome frame
documentation is all going through the secure server (slowly of course).

it. Thats why all the project expires dates are zero!

network interface.

in IR as "shN-X:Y", "shN-X", "shN:Y", or simply "shN", and they all
do the Right Thing.

list of nodes!

Unfortunately, doesn't give the obvious result for sharks since we changed
sh01 -> sh1, so no they are ordered: sh1, sh10 ... sh19, sh2, sh20, sh3, ...