GitLab

their experiments, via the experiment information page.

Noticed that I had a hard-coded test value still in the code ('lkwbox'
instead of $project; fixed that. Took out inclusion of Open2 package. Allow
a dash into the project name verification.

who have real shells on paper.

'cd <dir> ; command' (this is the only cirumstance where
these characters, or 'chained comands' are allowed). This
was done so that the wrapper script can use it, so that
the wrapper will work properly for people who have real
shells on paper.

webserver, as the uid of the experimentor. Not fully debugged yet
since the testbed has been kinda broken all day, but this needs to get
in if anyone else works on it.

some more work (taint checking), and possibly a splitup. Maybe have the
parsing code in one place and actual rebooting code and the like in
another place.

Add a top level rules file with common stuff like install rules.
Beef up tbsetup makefile, and include above files. Add install of all
the tbsetup programs to the bin dir and to the bogus lib/tbsetup
directory.

project approval section.

current umask, and so I don't get the protection value I want.
Too lazy to go figure it out, and adding a chmod was easiest!

to run a setuid script, but in this case, we want to allow it. Actually,
I'm not entirely sure that this restriction makes sense in our semi
controlled environment, but better safe than sorry. If you think I'm being
too paranoid, let me know.

Program must exist in the testbed bin directory.

all the scripts send output.
Remove test for group writable directory (where program exists). Too
paranoid and too inconvenient for all of us since it would require root
installs all the time.

aren't set up correctly, and a few misc. cleanups.

and checks the database to make sure that the actual UID running the
script has admin privs (admin == 1 in the user table). Will also run
as root/tbroot without checks. Intended to be called out of the web
interface in the project approval code.