1. 18 May, 2010 1 commit
  2. 17 May, 2010 1 commit
  3. 04 May, 2010 1 commit
  4. 21 Apr, 2010 1 commit
  5. 15 Apr, 2010 1 commit
  6. 13 Apr, 2010 1 commit
  7. 09 Feb, 2010 2 commits
  8. 20 Jul, 2009 1 commit
  9. 10 Jul, 2009 1 commit
  10. 09 Jul, 2009 1 commit
  11. 10 Jun, 2009 1 commit
  12. 20 Jan, 2009 1 commit
  13. 08 Sep, 2008 2 commits
  14. 19 Sep, 2007 1 commit
    • Russ Fish's avatar
      Move moduserinfo page form logic to a backend Perl script and methods. · 8965aad8
      Russ Fish authored
       GNUmakefile.in configure configure.in  - Add the testbed/backend directory.
       www/moduserinfo.php3 - The reworked PHP page.
       www/user_defs.php - Add a ModUserInfo method bridging to the script via XML,
           and remove the ChangeProfile method that is being replaced.
       backend/{moduserinfo,GNUmakefile}.in - Add the Perl script.
       db/User.pm.in - Add a ModUserInfo worker class method for script arg checking.
           Also SetUserInterface, SetWindowsPassword, and AccessCheck methods,
           and a copy of the escapeshellarg fn.
       sql/database-fill.sql - Add some to the table_regex 'users' checking patterns.
      
      Support stuff:
       account/tbacct.in - Update the UpdateWindowsPassword() function.
       db/libdb.pm.in - Add TBDB_USER_INTERFACE_EMULAB and TBDB_USER_INTERFACE_PLAB().
       tbsetup/libtestbed.pm.in - Add TB*EMAIL, TBMAIL_* vars (OPS, WWW, AUDIT).
      8965aad8
  15. 08 Aug, 2007 1 commit
  16. 25 May, 2007 1 commit
  17. 14 May, 2007 1 commit
  18. 14 Mar, 2007 1 commit
  19. 12 Mar, 2007 1 commit
  20. 09 Mar, 2007 1 commit
  21. 02 Mar, 2007 1 commit
    • David Johnson's avatar
      Adds rmcp support (for new wifi pcs) to the power command. For now, you · d31ab2bd
      David Johnson authored
      have to re-run the swig-wrappers target in tools/rmanage/GNUmakefile to
      generate the wrapper and perl module; this must of course be done when
      changes are made to the rmcp libs.
      
        * GNUmakefile.in, configure, configure.in: add tools/rmanage
        * tbsetup/GNUmakefile.in, tbsetup/power*.in: add rmcp to power command
        * tools/GNUmakefile.in: add rmanage
        * tools/rmanage/*.c,*.h: bugfixes, swig helper methods, etc.
        * tools/rmanage/rmcp.i: swig import control file
        * tools/rmanage/rmcp.pm,rmcp_wrap.c: rmcp wrapper/module generated by swig
      d31ab2bd
  22. 16 Jan, 2007 2 commits
  23. 10 Jan, 2007 1 commit
  24. 09 Jan, 2007 1 commit
    • Mike Hibler's avatar
      Frisbee MFS changes: · 346c0562
      Mike Hibler authored
       * support FreeBSD 6
       * client-side changes to support enable/disable of ACPI via slicefix
       * use dynamically linked Emulab binaries in frisbee MFS (for size)
      346c0562
  25. 15 Dec, 2006 1 commit
  26. 01 Dec, 2006 1 commit
  27. 25 Jul, 2006 1 commit
  28. 24 May, 2006 1 commit
  29. 31 Mar, 2006 1 commit
  30. 30 Mar, 2006 1 commit
  31. 02 Feb, 2006 1 commit
    • Timothy Stack's avatar
      · 0a4176c1
      Timothy Stack authored
      Various nfstrace changes that have been sitting in my tree for awhile.
      
      	* GNUmakefile.in: Do fs-install in the sensors subdir so the
      	nfstracer gets installed.
      
      	* sensors/and/and-emulab.priorities: Add some more daemon uid's to
      	be excluded from auto-nicing.
      
      	* sensors/and/and.c: Ignore invalid uids/gids in the config file
      	instead of dying.
      
      	* sensors/nfstrace/GNUmakefile: Makefile used to generate
      	nfsdb-create.sql.
      
      	* sensors/nfstrace/GNUmakefile.in: Some more installation stuff.
      
      	* sensors/nfstrace/nfsdb-create.sql: SQL used to create the nfsdb
      	database.
      
      	* sensors/nfstrace/nfsdump2db: Bunch of bug fixes and cleanup.
      
      	* sensors/nfstrace/nfsdump2db.8, sensors/nfstrace/nfstrace.7,
      	sensors/nfstrace/nfstrace.proxy.8: Start at some man pages.
      
      	* sensors/nfstrace/nfstrace.init.in: Try to detect the interface
      	to listen on, not perfect though.  Add a restart handler that just
      	restarts nfsdump2db.  Some other cleanup.
      
      	* sensors/nfstrace/nfstrace.proxy: Some optimizations for
      	resolving file names.
      
      	* sensors/nfstrace/nfsdump2/*: Only print summaries of read/write
      	packets and start a separate thread to read from the bpf socket.
      
      	* tbsetup/tbswap.in: Stop transferring nfs accesses to boss' db
      	until we figure out what we want to do with it.
      0a4176c1
  32. 26 Sep, 2005 1 commit
  33. 14 Sep, 2005 1 commit
    • Mike Hibler's avatar
      Changes related to allowing seperate 'fs' (file server) node. · c53d5827
      Mike Hibler authored
      Entailed new instructions for manual setup as well as integration into
      elabinelab framework.  First, the manual path:
      
      setup.txt, setup-boss.txt, setup-ops.txt and new setup-fs.txt:
          Updated to reflect potential for separate fs node.  The org here
          is a little dicey and could be confusing with ops+fs vs. ops and fs.
          Has not been field tested yet.
      
      */GNUmakefile.in: new fs-install target.
      
      configure, configure.in, defs-*:
          Somewhat unrelated, make min uid/gid to use be a defs setting.
          Also add config of fs-install.in script.
      
      boss-install.in, ops-install.in and new fs-install.in:
          Handle distinct fs node.  If you have one, fs-install is run before
          ops-install.  All scripts rely on the defs file settings of FSNODE
          and USERNODE to determine if the fs node is seperate.
      
      utils/checkquota.in:
          Just return "ok" if quotas are not used (i.e., if defs file FS_WITH_QUOTA
          string is null.
      
      install/ports/emulab-fs:
          Meta port for fs node specific stuff.  Also a patch for the samba port
          Makefile so it doesn't drag in CUPs, etc.  Note that the current samba
          port Makefile has this change, I am just backporting to our version.
      
      Elabinelab specific changes:
      
      elabinelab-withfs.ns:
          NS fragment used in conjunction with
      	tb-elab-in-elab-topology "withfs"
          to setup inner-elab with fs node.
      
      elabinelab.ns:
          The hard work on the boss side.  Recognize seperate-fs config and handle
          running of rc.mkelab on that node.  fs setup happens before ops setup.
      
      rc.mkelab:
          The hard work on the client side.  Recognize FsNode setup as well as
          differentiate ops+fs from ops setup.
      
      Related stuff either not part of the repo or checked in previously:
          emulab-fs package
      c53d5827
  34. 08 Sep, 2005 1 commit
  35. 19 Aug, 2005 1 commit
  36. 15 Aug, 2005 1 commit
    • Leigh B. Stoller's avatar
      The bulk of the mailman support. Still not turned on by default (cause · a64593f3
      Leigh B. Stoller authored
      Jay has "comments"), but I do not want it hanging around in my source
      tree. Here is my mail message:
      
      * The "My Mailing Lists" is context sensitive (copied from Tim's
        changes to the My Bug Databases). It takes you to the *archives* for
        the current project (or subgroup) list. Or it takes you to your
        first joined project.
      
      * The showproject and showgroup pages have direct links to the project
        and group specific archives. If you are in reddot mode, you also
        get a link to the admin page for the list. Note that project and
        group leaders are just plain members of these lists.
      
      * The interface to create a new "user" list is:
      
      	https://www.emulab.net/dev/stoller/newmmlist.php3
      
        We do not store the password, but just fire it over in the list
        creation process.
      
        Anyone can create their own mailing lists. They are not associated
        with projects, but just the person creating the list. That person
        is the list administrator and is given permission to access the
        configuration page.
      
        This page is not hooked in yet; not sure where.
      
      * Once you have your own lists, you user profile page includes a link
        in the sub menu: Show Mailman Lists. From this page you can delete
        lists, zap to the admin page, or change the admin password (which is
        really just a subpage of the admin page).
      
      * As usual, in reddot mode you can mess with anyone else's mailman lists,
        (via the magic of mailman cookies).
      
      * Note on cross machine login. The mailman stuff has a really easy way
        to generate the right kind of cookie to give users access. You can
        generate a cookie to give user access, or to the admin interface for
        a list (a different cookie). Behind the scenes, I ssh over and get
        the cookie, and set it in the user's browser from boss. When the
        browser is redirected over to ops, that cookie goes along and gives
        the user the requested access. No passwords need be sent around,
        since we do the authentication ourselves.
      a64593f3
  37. 03 Aug, 2005 1 commit