GitLab

clients so they can create a proper .forward file. 2) Add some
test code for seeing how feasible it is to do accounts on ops/tips
using tmcd instead of direct ssh. Initial results are not good; too
many accounts; does not scale well. Going to need a smarter protocol
for doing hundreds of accounts, but I will leave this code in place
for now. Note, unlike testbed nodes, control nodes must connect with
ssl.

Site-specific header graphic for gatech.

the hosts files that we put on free nodes. For reserved nodes, we
start a new hosts file from scrath, and qualify localhost with
the domain found from the hostname command.

and havoc upon all mankind and testbed users.

Before:
The main defs file (ie for configure) had an entry for WWWDEFS that
pointed to a <@WWWDEFS@>-defs.php3 file in the www/ directory. The www
defs file loaded some values about web pages, URLs, and some web
configuration parameters.

Problem:
Anything that was only in the www defs file was not accessible in the rest
of the universe (ie perl, C, and any other non-web-page scripts). For
instance, you couldn't have a perl script send an email to a user with a
link to the web site.

Solution:
Nuke all the www-defs files, move any important values into the main
configure, and change the web defs infrastructure to respect that. This
also meant adding about 3 lines each to all of the configure defs files.
(There really are about 10 new values you can change in your defs file,
but in almost all cases, the default values are the right thing.)

Upgrading:
External sites will need to move a few variables from their www-defs file
into their configure defs file. The example file should make it pretty
obvious. They may also want to customize some of the other vars that are
mentioned in configure.in and www/defs.php3.in .

work for virtual links when the node was a router, so pull them out
until I have the ipfw changes installed (the changes to use nexthop).

and when the last one was sent.

Subject: EMULAB.NET: 5 PCs idle 3 hours: gtecho/bar

think it is idle because it has been sent a swap request, but it isn't
really inactive, reset the swap request counter.

NOT have any options set.

clients so they can create a proper .forward file. 2) Add some
test code for seeing how feasible it is to do accounts on ops/tips
using tmcd instead of direct ssh. Initial results are not good; too
many accounts; does not scale well. Going to need a smarter protocol
for doing hundreds of accounts, but I will leave this code in place
for now. Note, unlike testbed nodes, control nodes must connect with
ssl.

shaping with them. Also a discussion of jails and how they relate, and a
proposed solution using MAC addresses (potentially made up ones) to
perform the demultiplexing at the receiving node.

bogus email to tbops, but rather spits the error directly to the
user.

swapfile.sys does not exist don't abort with an error message anymore.

we can send links that cause those fields to be filled in for people.
Add those links to email generated by newproject and newgroup pages
so that they can be saved by the leaders.

Add a bit of referrer magic to login page. When clicked from the join
or new project pages, tell login page to pass along the referrer page
so that when login is complete, user is zapped back to the original
page. This is especially nice when combined with the above change to
joinproject, whereby we send along the target pid/gid, but the user
has not yet logged in and remembers to do so via the link at the top
of the page.

make one in /usr/testbed/expwork/$pid. Too much cruft getting left
behind and it was causing even more log copy errors! Besides,
typically its just tbops people who need to look at that stuff.

I've fixed all existing group directories.

just like /proj/$pid.

in /proj/$pid/exp/$eid, since this would seem to violate group
privacy (/proj exported to all experiments). Minor changes to owner
and mode to allow for non group members to swap/terminate and not get
copy error (of logs).

it was causing copy errors when non-group members try to swap an
experiment. Make it 664 instead.

In addition to the usual checks, project_root and group_root (in the
project) get the same permission as if they were in the subgroups with
group_root permission. This means they can swap/terminate/reboot etc
in subgroups even though they are not members of the subgroups.
There is still some copy problems with files, but leaving that till
later to deal with.

wrt subgroups. Also noted that group created is no longer in the group
by default.

project pages. Also fix the group one to be more consistent with the
others.

-s is now required to set bits, and there is a -p option so that you
can give physical node names.