added what we check for activity, and changed things from "24 hours" and
such to "several hours" and "a few hours".

would have the netbed header not get included as a header, but as the
first line of the body. Moving the headers above the subject fixes it.

1. timeouts for nodes weren't getting reset when they had a mode
ransition, so they were timing out in shutdown after changing modes.
2. It was still going back into a blocking wait, even though a signal had
been recieved, and not quitting back up to the main loop to handle it.

in the environment to decendants once the the audit is done.

no nodes in the expt. (The lib assumed the expt didn't exist if it didn't
find any nodes for it.)

NOTE: You have to gmake clean the event/sched/ dir before this will get
built in properly! Don't install your version without it!

have left in place.

code when taking a signal.

experiments look more like regular experiments. Batch mode experiments
can now be preloaded and swapped. When preloaded, they go into a
"Pause" state. Swapping a batch mode experiment in puts them into the
"posted" state so the batch daemon will see them. Swapping out a
batchmode experiment does the expected; it puts them back into the
Pause state. Terminating a batch mode experiment does the expected;
its gone. When a batch mode experiment finishes normally, it goes back
into the pause state, which allows batches to be reinjected as many
times as Eric likes.

memory leak in one of the timeout queue data structures, more or less.

Also do some prep work to carry $idleswap and $autoswap through this
script like $force is. (For calling the back end with different params,
when it supports it.)

returned for all users. Actually, it was just not resetting the
count back to zero, so all users got their groups, plus a few extra.

each portion of the experiment as it is modified.

Also add expt_swap_uid so that we know who did the last operation, and
so we can charge/credit the right person. So, if joe swaps in the
experiment and jane swaps it out, joe gets charged. If jane swaps in
the experiment and joe modifies it, jane gets credit for the first
portion, and joe will later get charged for the second portion.

Took longer to explain then to implement ...

Lbs

Changed submit button to work on NS4.7
(by using <input type='submit'> instead of <button>)
for our retrocomputing friends.

seconds (on a DSL line). (Also decreases db load...)
Some of the defaults were as high as 400 records. Dropping them to 100
took the generated page from over 100KB to 31KB.

Later (someday) we can add stuff to easily change the number of records
you request, and perhaps even change the starting point to something
other than the most recent stuff.

didn't see in testing. Specifically, why it pegs at 100% CPU after a
while, and why it gets timeouts after it has removed the timeout from the
queue.

Temporarily make TCSH the only option until Leigh gets new images
together.

Users can, via, moduserinfo, set a preferred shell.
One of {tcsh, bash, csh, sh}.
When users are created, they are given tcsh.
All users which already exist have been given tcsh.

1. Change from inefficient timeout search algo that ran once per second to
a highly efficient priority queue method of managing timeouts. Now
instead of checking every node's timestamps, we just look at the head of
the queue, and it is often much less frequent than once a second, since we
know how long we have until the next timeout.

2. Start using a blocking poll for events, so I can sleep for long periods
of time instead of having to wake up at least once a second to check for
timeouts and events. Will set the block timeout for the shortest of: the
time to send out the next batch of queued emails, the next time a timeout
may occur, or when there are no mails waiting and no timeouts possible, 10
minutes. Comes back as soon as an event comes in.

3. Given the above two items, we no longer need a sleep(1) in our main
loop.

One small glitch is in the progress of being fixed. When using blocking
polls, things hang when trying to unregister from the event system. Not a
big deal, just ^C twice to kill it. (May cause it to need two SIGUSR1's
to get it to restart, too.)

In the next update, look for:
 - Really take action on timeouts.
   - keep track of how many times we've retried, and notify if something
     may be wrong with the node.
   - Find out policy on taking action with timeouts.
     - Do it if the expt is in transition or the node is free
     - Probably don't touch if the expt is established.
     - Maybe? in active expt, send (good) email to expt owner on timeouts

Related "coming soon" items:
os_load/os_setup etc.:
 - Add the waitforstate stuff we've talked about
 - make os_load/os_setup use it

be quick and efficient for the types of operations that stated needs to
make with its timeout queue. But still pretty general, I think.

system now to do scheduling. Instead just show last swap/modify time,
along with the uid of the person who did it.

Report on per-class node counts instead of the total number, since
with virtual nodes it is better to split that number up.

per Shashi's request.

what veth interfaces belong to which jail node.

newnodecheckin.php accepts some information about a new node, tries to
figure out a node_id, IP, type, etc. for them, sticks this into the
new_ tables, then alerts testbed-ops. Another (not yet created) page
will be used to make the new node a real boy.

newclient will run from a (not yet created) MFS - it collects various
data about the node, like its MAC, runs teachswitch, and checks in
via newnodecheckin.php .

to swap in/out/modify an experiment, so we can do proper accounting.

dojailconfig: Do not return a jail config unless the node is really
jailed.

doifconfig: Look at the node name, and return ifconfig info specific
to the name instead of always returning all info for the machine. Upon
boot, virtual interfaces will not be setup, but instead will be setup
when the jail is setup. When the jail requests ifconfig info, it gets
only its list of interfaces to setup.

dolinkdelays: Ditto, since linkdelays will be setup after per-jail
interfaces are setup.

real life.

There's a small window in time (typically a few seconds, but maybe 10's of
seconds on occasion) between the time nodes get nalloc'd and the time they
get rebooted during a swapin. If idlemail runs (or someone views a web
page) during this time, the expt can appear idle because the nodes haven't
had any activity. It can cause an incorrect email or a false positive on
the web page.

The fix is to have nalloc register some external node activity, like
node_reboot does, when it allocates a node.