1. 09 Feb, 2018 1 commit
  2. 05 Feb, 2016 1 commit
  3. 24 Sep, 2012 1 commit
    • Eric Eide's avatar
      Replace license symbols with {{{ }}}-enclosed license blocks. · 6df609a9
      Eric Eide authored
      This commit is intended to makes the license status of Emulab and
      ProtoGENI source files more clear.  It replaces license symbols like
      "EMULAB-COPYRIGHT" and "GENIPUBLIC-COPYRIGHT" with {{{ }}}-delimited
      blocks that contain actual license statements.
      This change was driven by the fact that today, most people acquire and
      track Emulab and ProtoGENI sources via git.
      Before the Emulab source code was kept in git, the Flux Research Group
      at the University of Utah would roll distributions by making tar
      files.  As part of that process, the Flux Group would replace the
      license symbols in the source files with actual license statements.
      When the Flux Group moved to git, people outside of the group started
      to see the source files with the "unexpanded" symbols.  This meant
      that people acquired source files without actual license statements in
      them.  All the relevant files had Utah *copyright* statements in them,
      but without the expanded *license* statements, the licensing status of
      the source files was unclear.
      This commit is intended to clear up that confusion.
      Most Utah-copyrighted files in the Emulab source tree are distributed
      under the terms of the Affero GNU General Public License, version 3
      Most Utah-copyrighted files related to ProtoGENI are distributed under
      the terms of the GENI Public License, which is a BSD-like open-source
      Some Utah-copyrighted files in the Emulab source tree are distributed
      under the terms of the GNU Lesser General Public License, version 2.1
  4. 08 Sep, 2008 1 commit
  5. 09 Jan, 2007 1 commit
  6. 08 Sep, 2005 1 commit
  7. 11 Oct, 2004 1 commit
  8. 31 Mar, 2004 2 commits
    • Mike Hibler's avatar
      Properly compute timestamp differences. Lets see how things work now that · bfecdbeb
      Mike Hibler authored
      we don't report 100 sec/min and 10000 sec/hour!
    • Mike Hibler's avatar
      Another Mike Piss-fest: · c9a2f065
      Mike Hibler authored
      1. Work on the query some more.  Make the various clauses that matched node
         types more precise.  Previously for example, plab dslices were potentially
         matching the vnode clause because the latter only check that something was
         a virtnode, which plabdslices are.
      2. Watchout for 0 timeout values which are supposed to mean no timeout
         (but would have meant immediate timeout here)
      3. Dink with the logging.
  9. 25 Mar, 2004 1 commit
  10. 16 Mar, 2004 2 commits
  11. 31 Dec, 2003 2 commits
  12. 28 Dec, 2003 2 commits
  13. 16 Dec, 2003 1 commit
  14. 03 Feb, 2003 2 commits
  15. 02 Feb, 2003 1 commit
  16. 04 Jul, 2002 1 commit
  17. 20 Jun, 2002 1 commit
    • Leigh B. Stoller's avatar
      Change query; do not ping remote, virtual, or those stinky fishlike · a9a6b32d
      Leigh B. Stoller authored
      Add handler for remote nodes, which now report keepalive once a
      minute. Simply look at the timestamp and change status from up to
      down if it has not responded in more than 90 seconds. This is kinda
      crude, and mostly for the benefit of the web page. The wan solver
      will use the timestamps directly.
  18. 11 Feb, 2002 1 commit
  19. 27 Sep, 2001 1 commit
    • Robert Ricci's avatar
      Lib-ification. These scripts have been changed from using the Mysql module to · 4c11aa5d
      Robert Ricci authored
      using the libdb library. They have also been cleaned up somewhat, with more
      comments added, etc.
      I've merged nodeip and mac2if, which had very similar functions. The merged
      version goes under the name nodeip.
      Lastly, I've added some access checks to db2ns and node_status, to make sure
      they're only called by the right people.
  20. 23 May, 2001 1 commit
    • Robert Ricci's avatar
      node_status: Updates the 'status' column of the 'nodes' table of the database · 5a9e29e8
      Robert Ricci authored
      Possible statuses are: "up","possbily down","down","unpingable"
      "possibly down" indicates that a node has looked down for 1 run of node_status -
      next time node_status is run, it will be set to 'down' if it still doesn't
      "unpingable" indicates that a node is beleived to be running an OS that does
      not reply to pings, so we can't tell if it's up or down