1. 19 Jun, 2002 1 commit
  2. 13 Jun, 2002 1 commit
  3. 12 Jun, 2002 3 commits
  4. 10 Jun, 2002 1 commit
  5. 07 Jun, 2002 1 commit
  6. 28 May, 2002 1 commit
  7. 27 May, 2002 1 commit
  8. 23 May, 2002 1 commit
  9. 20 May, 2002 1 commit
  10. 15 May, 2002 1 commit
  11. 14 May, 2002 1 commit
  12. 13 May, 2002 1 commit
  13. 10 May, 2002 2 commits
  14. 06 May, 2002 2 commits
  15. 05 May, 2002 1 commit
  16. 02 May, 2002 1 commit
  17. 25 Apr, 2002 2 commits
  18. 24 Apr, 2002 2 commits
    • Mike Hibler's avatar
      bug fix to make reset command work with UDP · 8a29d3c4
      Mike Hibler authored
      8a29d3c4
    • Mike Hibler's avatar
      Support for a "reset" command to close existing connection. · 503e9a26
      Mike Hibler authored
      Also fixed bug where changing packet size would change an explicitly
      specified packet rate because we only tracked the packet interval.  E.g.:
      	set packetSize_=100
      	set rate_=100
      would result in a packet rate of 100Kbps, but then doing:
      	set packetSize_=1000
      would result in a packet rate of 1000Kbps even though the rate was not
      explicitly changed.  Now we actually keep track of whether the rate was
      explicitly set and, if so, change the interval to maintain the rate.
      503e9a26
  19. 23 Apr, 2002 1 commit
    • Leigh Stoller's avatar
      Fix original source error; A dynamic event with a shorter timeout did not · fec09f29
      Leigh Stoller authored
      interupt the current next up event cause Ian's code just grabbed it
      off the queue and went into select. I converted this code to use a
      condition variable and a timed wait. If a new event comes in, signal
      the waiter who can recheck to see of the head of the queue has
      changed. Seems to work, but not well tested. This bug reported by Rob!
      fec09f29
  20. 19 Apr, 2002 1 commit
  21. 16 Apr, 2002 1 commit
  22. 11 Apr, 2002 1 commit
  23. 10 Apr, 2002 1 commit
    • Robert Ricci's avatar
      First pass at operational mode support for node states. · 4db415f5
      Robert Ricci authored
      Operational mode (op_mode in the database) affects the state diagram
      and timeouts for a node. Modes planned so far are:
      NORMAL    - Normal operation
      DELAYING  - Acting as a delay node
      UNKNOWNOS - Running an OS that does not report its state (OSKit kernels, etc.)
      RELOADING - Disk reloading
      
      stated now responds to to TBNODEOPMODE events, and sets database state
      accordingly. The set of state timeouts and valid state transitions are
      affected by a node's operational mode.
      
      The nodes table now stores information about operational modes, and
      the state_transitions and state_timeouts tables include the operational
      mode in addition to states.
      
      Next step will be to get the appropriate programs to send TBNODEOPMODE
      events.
      4db415f5
  24. 09 Apr, 2002 1 commit
  25. 04 Apr, 2002 1 commit
  26. 03 Apr, 2002 3 commits
  27. 02 Apr, 2002 3 commits
  28. 01 Apr, 2002 3 commits