GitLab

just add seconds to it - It's in 'YYYYMMDDHHMMSS' format rather than a
UNIX-style second count. So, the solution I came up with (not sure if it's
the best one) is:
(CURRENT_TIMESTAMP - INTERVAL $warn_time MINUTE) > rsrv_time

all those top and ptop files are collecting in /usr/testbed/www!

linked list has been set up, don't just return. Instead, set a return value
variable and GOTO the bottom of the function where the code to free this
list lives.

with a dated name. That way I can go back and look at the exports file
that was in use at the time it died, since it almost looks to me like
the exports file is messed up in some way that is not being caught by
mountd when it reads it.

than trying to infer how long a node has been reserved by polling the contents
of the reserved table, use the timestamp in that table, which I didn't notice
the first time through. Makes the code much simpler and more correct.

a '-n' option to use netdisk, and will respond properly to changing
TB_DEFAULT_RELOADTYPE in libdb.

os_load also got some fixes for the -w flag when used with Frisbee - it fires
off all nodes at once, rather than two at once.

check box means. Also add links from the begin experiment page and
from the experiment information page to the FAQ entry. Lets see if
this helps.

netdisk is handled properly, since it never does a 'tmcc reset'.

Elvin server discovery protocol.

read. The impl (menu stuff) needs to be cleaned up for sure.

TB_IMAGEID_READINFO - I was mistaken about the level of access implied
by TB_IMAGEID_ACCESS.

currently defined as 30 minutes, to keep false positives to a minimum. Sends
mail to testbed-ops if/when it finds any. The timing is not precise, as it
only polls in between loading machines, but this is fine for our purposes.

people who want to log into the delay nodes and change a specific link.

stuff so that the web page did not need to do anything except display
and form processing. Add tbsetup/node_control for backend so that it
can be called from the command line too. The virt_nodes table is also
updated (for those values that have virt_nodes equivalents), and this
mostly implies that changes can be applied only to swapped in
experiments since we use the reserved table to map pcXXX to its vname
so that the virt_nodes table can be updated. It is an easy extension
to allow changes based on the pid/eid/vname, but I do not see a reason
to support this ability yet. Note usage:

    Usage: node_control name=value [name=value ...] node [node ...]
           node_control -e pid,eid name=value [name=value ...]
           node_control -l
    For multiword values, use name='word0 ... wordN'
    Use -l to get a list of operational parameters you can change.
    Use -e to change parameters of all nodes in an experiment.

    {824} stolle...

request.

whose idea was that. Oh right, mine.

a lurking case where GID is null. Need to find that, but in the
meantime this will keep the tmcd happy.

there have been 260,000 connects (and 260,000 disconnects) to the
mysqld server. 240,000 of them were from the TMCD! I've changed the DB
code to keep the connection to the server open, and let the server
time it out. The client side code library code already deals with a
auto reconnect if the server goes away, so no reason to open/close
this connection for every single DB query. Besides, it might help
reduce the amount of time it takes to answer a single tmcd query, and
that would be a good thing.

Made this number more easily tweakable: just set $max_tries in vlanLock().
Also, only prints out every 5th failure, and in a form that should make it
more clear that it's a transient, recoverable, error.

was preventing VLANs from being cleared out before they were delted.

document.