Skip to content
  • Leigh B. Stoller's avatar
    * Removed startexp, and merged its contents into batchexp. There has been · aef08532
    Leigh B. Stoller authored
      no reason for the separation for a long time, and it made maintence more
      difficult cause of duplication between batchexp and startexp (batch was
      the sole user of startexp). Cleaner solution.
    
    * Check argument processing for batchexp, swapexp, endexp to make sure the
      taint checks are correct. All three of these scripts will now be
      available from ops. I especially watch the filename processing, which was
      pretty loose before and could allow some to grab a file on boss by trying
      to use it as an NS file (scripts all runs as user of course). The web
      interface generates filenames that are hard to guess, so rather then
      wrapping these scripts when invoked from ops, just allow the usual paths
      (/proj, /groups, /users) but also /tmp/$uid-XXXXXX.nsfile pattern, which
      should be hard enough to guess that users will not be able to get
      anything they are not supposed to.
    
    * Add -w (waitmode) options to all three scripts. In waitmode, the backend
      detaches, but the parent remains waiting for the child to finish so it
      can exit with the appropriate status (for scripting). The user can
      interrupt (^C), but it has no effect on the backend; it just kills the
      parent side that is waiting (backend is in a new session ID). Log outout
      still goes to the file (available from web page) and is emailed.
    aef08532