but does make mail headers for devel trees much more descriptive.

idlemail <pid> <eid> instead, with the optional -f force, to be able to
send a swap request even when the expt isn't idle (or is idle ignored, or
it hasn't been long enough since the last one, etc.)

instead (so the exit status could be checked in the if condition!).

from the command line.

are packed 1) Add trivial_ok flag to virt_lans table. Global to the
lan or link, allow nodes in the lan or link to be colocated on the
same phys node. Perhaps make it per-node at some point. 2) Add
multiplex_factor to the experiments table to allow user to override
the multiplex_factor that is contained in the node_types table. Make
per type at some point.

them.

Make user profile toggle for admin mode use toggle.php too.)

Fix Eric's nit about showing no estimate before we have one to offer.

   noswap_reason tinytext			- The reason they're unswappable
   idleswap tinyint(4) NOT NULL default '0'	- The idleswap bit (for auto. idleswap)
   idleswap_timeout int(4) NOT NULL default '0'	- The timeout for idleswap (in minutes)
   noidleswap_reason tinytext			- The reason they're non-idleswap
   autoswap tinyint(4) NOT NULL default '0'	- The autoswap bit
   autoswap_timeout int(4) NOT NULL default '0'	- The timeout for autoswap (in minutes)

The new form for expt create should fill these in, and swapin will update the idleswap
timeout if idleswap is set. Idlemail will read these and do the deed as needed.
They'll also get shown on the new expt display page.

As soon as we move to the new form, we can nuke priority.

in the full set of subgroups, which can break swapping an experiment
created in a subgroup.

back end scripts now support 3 different kind of forced swaps:

1. Idle-Swap : this is ths same one we had before. Email message to them
says it was swapped "because it was idle for too long"

2. Auto-Swap : A new one, typically for user-requested timed swapouts.
Email says it was swapped "because it was swapped in too long"

3. Force swap: Generic one, for "none of the above" cases. Just says
Experiment "has been forcibly swapped out by Testbed Operations."

The force swap option on the web now lets you choose which of these three
you want. Only "Idle-Swap" counts as an idleswap in the stats. Soon
idleswap and autoswap will be used by idlemail when it does automatic
swapping.

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.