1. 19 Jul, 2011 1 commit
  2. 14 Jul, 2011 1 commit
  3. 13 May, 2011 1 commit
  4. 11 May, 2011 1 commit
  5. 29 Apr, 2011 1 commit
  6. 21 Mar, 2011 1 commit
  7. 07 Mar, 2011 1 commit
  8. 02 Mar, 2011 1 commit
  9. 01 Mar, 2011 1 commit
  10. 24 Feb, 2011 1 commit
  11. 23 Feb, 2011 1 commit
  12. 18 Jan, 2011 1 commit
  13. 06 Jan, 2011 1 commit
  14. 27 Dec, 2010 1 commit
  15. 23 Dec, 2010 2 commits
  16. 22 Dec, 2010 2 commits
  17. 20 Dec, 2010 1 commit
  18. 15 Dec, 2010 1 commit
  19. 16 Nov, 2010 1 commit
    • Kevin Atkinson's avatar
      Add support for all node "tb-set-tarfiles". · a0d0c95e
      Kevin Atkinson authored
      "tb-set-tarfiles" is like "tb-set-node-tarfiles" except that it
      distributes the tarfile to all nodes rather than just one and that it
      uses frisbee to distribute the file.
      
      These changes involved 1) refactoring frisbee info from images table
      into a new table, frisbee_blobs, 2) a new experiment_blobs table, and
      3) a new tmcd command so the node knows how to get the files from the
      server.
      
      The changes where designed to be general purpose enough to eventually
      support:
        1) Distributing arbitrary files (not just tarfiles) to nodes
        2) Perform arbitrary actions on those files
        3) Use arbitrary methods to get the files
      
      As such the tmcd line is as follows:
        URL=* ACTION=*
      
      where URL is currently:
        frisbee.mcast://<ADDR>/<FILE>
      for example
        frisbee.mcast://234.16.184.192:18092/users/kevina/home-dir.tar.gz
      and when we get around to using a master Frisbee server it could be
        frisbee://*
      or it could be a file://, http://, etc.
      
      and ACTION is currently:
        unpack:<LOCATION>
      for example
        unpackt:/users
      with future syntax to be determined.
      a0d0c95e
  20. 09 Nov, 2010 1 commit
  21. 15 Oct, 2010 1 commit
  22. 01 Oct, 2010 1 commit
    • Kevin Atkinson's avatar
      Bug fix: Don't assume fgets when reading from a socket will always return data. · 824fab48
      Kevin Atkinson authored
      In fact, it might return an empty string if there is no data available.
      Thus testing trim(fgets(...))=='' is NOT a good way to test for a
      blank line.  Fixed this by accounting for the no data case.
      
      This bug caused the header of the HTTP response of an xmlrpc call to
      become part of the body, and thus creating invalid xml, which in turn
      caused xmlrpc_decode_request to fail.  The end result was that a WEB
      ERROR REPORT was created and no useful info was returned to the user
      when an NS file took a long time to parse.
      824fab48
  23. 29 Sep, 2010 2 commits
  24. 21 Sep, 2010 1 commit
  25. 17 Sep, 2010 1 commit
  26. 08 Sep, 2010 1 commit
  27. 07 Sep, 2010 1 commit
  28. 03 Sep, 2010 1 commit
  29. 09 Aug, 2010 1 commit
  30. 02 Aug, 2010 1 commit
  31. 30 Jul, 2010 1 commit
  32. 24 Jul, 2010 1 commit
  33. 19 Jul, 2010 1 commit
  34. 18 Jul, 2010 2 commits
  35. 16 Jul, 2010 2 commits