1. 31 Oct, 2005 1 commit
  2. 28 Oct, 2005 1 commit
    • Leigh B. Stoller's avatar
      Rework to use an iframe for most of the work, rather then sajax. Still · 3805c04e
      Leigh B. Stoller authored
      using a sajax call for cancelation, but the main invocation uses a
      plain iframe. This has the added benefit of scrolling more nicely
      instead of jumping back to the top with each write.
      
      Looks like xmlhttprequest or its impl in at least firefox is
      moderately broken, so that mulitple simultaneous requests get very
      confused with each other, and things break.
      3805c04e
  3. 18 Oct, 2005 1 commit
  4. 10 Sep, 2004 1 commit
    • Leigh B. Stoller's avatar
      Small change to suexec code. This change has the potential for creating · 7e731fba
      Leigh B. Stoller authored
      unanticipated breakage. If that happens, just need to back out the
      changes under the "suexec-stuff" tag. However, the better solution will
      probably be to fix the PHP scripts that break by adding the proper
      groups in the call to suexec (in the web page, see below) or by fixing
      the backend Perl script that breaks.
      
      This fix is primarily to address the problem of some users being in more
      groups (cause of subgroups) then the max number of groups allowed
      (NGROUPS).  The groups that really mattered (say, for creating an
      experiment in a subgroup) could be left out cause they were at the end
      of the list.
      
      * suexec.c: Change how groups are handled. Instead of taking a single
        gid argument (the gid to setgid as), now takes a comma separated list
        of groups. Further, instead of doing a setgroups to the user's entire
        group list as specified in the groups file (getgroups), setgroups to
        just the groups listed on the command line, plus the user's primary
        group from the password file (this is to prevent potential breakage
        with accessing files from the users homedir, although might not really
        be necessary).
      
        This change is somewhat rational in the sense that in our case, suexec
        is not being used to run arbitrary user code (CGIs), but only to run
        specific scripts that we say should be run. The environment for
        running those scripts can be more tightly controlled then it would
        otherwise need to be if running some random CGI the user has in his
        public html directory.
      
      * www: Change the gid argument to SUEXEC() in a number of scripts so
        that the project and subgroup are explicitly given to suexec, as
        described above. For example, in beginexp:
      
      	SUEXEC(gid, "$pid,$unix_gid", ....);
      
        Aside: note that project names (pid) are always one to one with their
        unix group name, but subgroup names are not, and *always* have to be
        looked up in the DB, hence the "unix_gid" argument.
      
        Script breakage should require nothing more then adding the proper
        group to the list as above.
      7e731fba
  5. 12 Jul, 2004 1 commit
  6. 30 Jun, 2004 1 commit
  7. 29 Jun, 2004 3 commits
    • Leigh B. Stoller's avatar
      Spit out a bunch of blanks (1024 of them) to get past the browser · 39a67a54
      Leigh B. Stoller authored
      buffering so that it will start to display output line by line.
      1024 for Firefox, probably the same for Netscape. I hear that IE is
      256 bytes.
      39a67a54
    • Leigh B. Stoller's avatar
      Ack, this comment refers to previous revision. · f1c5ee39
      Leigh B. Stoller authored
      * Changed the linktest web page to allow for killing a running
        linktest when called from the showexp page. Puts up a simple Click
        form, whose action is to call "linktest_control -k" which does the
        dirty work.
      
      * Implement a simple frameset when running linktest. I did this cause
        it was something new and besides, it was more fun then trying to
        reverse engineer the modelnet model file. Anyway, when linktest is
        started, put up a new window that has a two window frameset. The
        right hand window is just the spew output from linktest as it runs
        (although with buffering not much turns up at first). The left side
        window has a single click box to stop the running linktest, whose
        action is to call linktest_control -k as above. By the magic of
        javascript, when the linktest finishes, the stop button is removed
        and replaced with a "Linktest Finished" message. So exciting.
      f1c5ee39
    • Leigh B. Stoller's avatar
      Minor change to "Run Linktest" menu option; when the is a non-zero pid · e0a72dc6
      Leigh B. Stoller authored
      in the DB, change that to Stop Linktest instead.
      e0a72dc6
  8. 29 Apr, 2004 1 commit
    • Leigh B. Stoller's avatar
      Add prelim support for using linktest. Because of problems, this is · 6cdccbd2
      Leigh B. Stoller authored
      currently available to only people with stud=1 status in the DB.
      
      * www/tbauth.php3: Add a STUDLY() function to check that bit.
      
      * www/linktest.php3: New page to run linktest on the fly. The level
        defaults to the current level in the experiments table, but you can
        override that via the form on the page.
      
      * www/showexp.php3: Add link to aforementioned page. STUDLY() only.
      
      * www/beginexp_form.php3: Add an option (selection) to set the linktest
        level for create/swapin. Defaults to 0 (no linktest). STUDLY() only.
      
      * www/editexp.php3: Add an option to edit the default linktest level
        for an experiment. STUDLY() only.
      
      * tbsetup/batchexp.in and tbsetup/swapexp.in: Add code to optionally run
        the linktest, sending email if it fails (exists with non-zero status).
        Failure does not affect the swapin.
      6cdccbd2