1. 11 Apr, 2006 1 commit
  2. 26 May, 2005 1 commit
  3. 20 May, 2005 1 commit
  4. 24 Jun, 2004 1 commit
    • Mike Hibler's avatar
      Improve the client-side install. With these changes, it should now be · 976133e4
      Mike Hibler authored
      possible to:
      	gmake client
      	sudo gmake client-install
      on a FBSD4, FBSD5, RHL7.3, and RHL9.0 client node.
      There are still some dependencies that are not explicit and which would
      prevent a build/install from working on a "clean" OS.  Two that I know of are:
      you must install our version of the elvin libraries and you must install boost.
  5. 06 Oct, 2003 1 commit
    • Leigh B. Stoller's avatar
      * New libtmcc.pm module that encapsulates the tmcc interface. Most of the · 434a472a
      Leigh B. Stoller authored
        code that was in libsetup has moved into this library, and underwent a
        giant cleaning and pumping up. The interface from your typical perl
        script now looks like this:
        use libtmcc;
        if (tmcc(TMCCCMD_STATUS, "optional arguments", \@tmccresults) < 0) {
            warn("*** WARNING: Could not get status from server!\n");
            return -1;
        foreach my $me (@tmccresults) {
      	print "bite $me";
        The arguments and results are optional values. There is a fourth optional
        value that is a hash of config options (basically converted to command
        line switches passed to tmcc). For example, to set the timeout on an
        individual call, pass a fourth argument like:
      	("timeout" => 5)
        There is also a way to set global options so that all subsequent tmcc
        calls are affected:
      	configtmcc("timeout", 5);
        I'll probably clean this up a bit to avoid the direct strings.
        The result list is a list of strings. Since we are trending away from
        using tmcc to transfer large amounts of data, I think this is okay.
      * A new tmcc.pl which does little more than load libtmcc and use it.
        This will become the new tmcc, with the existing C version becoming a
        backend binary for it.
      * All of the perl scripts in tmcd have been changed to use the new
        library. I left the few uses of tmcc in shell scripts alone since they
        were of the simple variety (mostly "state" command).
      * And again, if you have read this far, you will learn why I bothered with
        all this. Well, the existing code was really bad and it was getting out
        of control. Sort of like a squid that was getting harder to control as
        its rotting tenticles slithered into more and more scripts. Anyway ...
        More important, my goal is to use the libtmcc library to add caching.  I
        have not worked out the details yet, but I am envisioning a configuration
        file, perhaps generated initially by tmcd, of all of the config
        values. If the library finds that file, it sucks the info out of the file
        instead of going to tmcd. Eventually, this config file would be generated
        as part of experiment swapping and stored in the DB, but thats a longer
        term project, and perhaps orthogonal (how we fill the cache is not as
        important as adding the ability to use a cache, right?).
        Note that certain operations (like "state" and "ready") are flagged by
        the library to always bypass the "cache".
  6. 24 Jun, 2003 1 commit
  7. 21 Apr, 2003 1 commit
  8. 17 Apr, 2003 1 commit
  9. 23 Dec, 2002 1 commit
  10. 20 Dec, 2002 6 commits
  11. 18 Dec, 2002 3 commits
  12. 10 Sep, 2002 1 commit
  13. 03 Sep, 2002 1 commit
  14. 27 Aug, 2002 1 commit
  15. 20 Aug, 2002 1 commit
  16. 15 Aug, 2002 1 commit
  17. 29 Jul, 2002 1 commit
    • Leigh B. Stoller's avatar
      A wide array of little changes to improve the distribution of the · f066d2d9
      Leigh B. Stoller authored
      client software to widearea nodes. Most of these changes were to
      reduce the embarrassment factor. At some point we need a proper
      autoconf and such, but for now there is a makefile in the src dir for
      creating the distribution.
      I've tested it on a local linux node and mostly on a freebsd node, but
      I've moved things around and so updating the RON nodes will require
      some hand intervention by me at some point.
  18. 10 Jul, 2002 1 commit
  19. 07 Jul, 2002 1 commit
  20. 02 Jul, 2002 4 commits
  21. 19 Jun, 2002 5 commits
  22. 06 Jun, 2002 3 commits
  23. 31 May, 2002 2 commits
    • Leigh B. Stoller's avatar
      New watchdog daemon for remote (RON) nodes. Okay, not much of a · 6c44b4a4
      Leigh B. Stoller authored
      watchdog at the moment, but it will be. Right now it does boot time
      stuff; issues tmcc state event so the testbed knows (REBOOTED), does
      an account update to get any accounts missed while dead, then sets up
      and vnodes (tunnels and such) that where supposed to be running on
      the node, then issues a tmcc ISUP event.
      After that, goes into a loop doing periodic account update. At some
      point it would be good to look for stale vnodes (that could not be
      torn down because of network connectivity problems), but there are
      some race conditions that I need to work out first.
    • Leigh B. Stoller's avatar