1. 28 May, 2003 4 commits
  2. 27 May, 2003 5 commits
  3. 26 May, 2003 2 commits
  4. 25 May, 2003 1 commit
  5. 24 May, 2003 4 commits
  6. 23 May, 2003 5 commits
  7. 22 May, 2003 9 commits
  8. 21 May, 2003 5 commits
    • Chad Barb's avatar
      Minor typos · 9ef4d24e
      Chad Barb authored
      9ef4d24e
    • Leigh B. Stoller's avatar
      Minor stats changes for dealing with swapmodify; be sure to credit for · cb309ff2
      Leigh B. Stoller authored
      each portion of the experiment as it is modified.
      
      Also add expt_swap_uid so that we know who did the last operation, and
      so we can charge/credit the right person. So, if joe swaps in the
      experiment and jane swaps it out, joe gets charged. If jane swaps in
      the experiment and joe modifies it, jane gets credit for the first
      portion, and joe will later get charged for the second portion.
      
      Took longer to explain then to implement ...
      
      Lbs
      cb309ff2
    • Chad Barb's avatar
      · f3a7da49
      Chad Barb authored
      Changed submit button to work on NS4.7
      (by using <input type='submit'> instead of <button>)
      for our retrocomputing friends.
      f3a7da49
    • Mac Newbold's avatar
      Cut down the default number of records, to get the page load time under 10 · 9cc5955f
      Mac Newbold authored
      seconds (on a DSL line). (Also decreases db load...)
      Some of the defaults were as high as 400 records. Dropping them to 100
      took the generated page from over 100KB to 31KB.
      
      Later (someday) we can add stuff to easily change the number of records
      you request, and perhaps even change the starting point to something
      other than the most recent stuff.
      9cc5955f
    • Leigh B. Stoller's avatar
  9. 20 May, 2003 5 commits
    • Mac Newbold's avatar
      Back out last set of changes until we figure out some odd behaviors that I · 1934cc59
      Mac Newbold authored
      didn't see in testing. Specifically, why it pegs at 100% CPU after a
      while, and why it gets timeouts after it has removed the timeout from the
      queue.
      1934cc59
    • Chad Barb's avatar
      · fc1f5080
      Chad Barb authored
      Temporarily make TCSH the only option until Leigh gets new images
      together.
      fc1f5080
    • Chad Barb's avatar
      · 4df405d6
      Chad Barb authored
      Users can, via, moduserinfo, set a preferred shell.
      One of {tcsh, bash, csh, sh}.
      When users are created, they are given tcsh.
      All users which already exist have been given tcsh.
      4df405d6
    • Mac Newbold's avatar
      Bunch of pretty good-sized changes to stated: · b438d5f5
      Mac Newbold authored
      1. Change from inefficient timeout search algo that ran once per second to
      a highly efficient priority queue method of managing timeouts. Now
      instead of checking every node's timestamps, we just look at the head of
      the queue, and it is often much less frequent than once a second, since we
      know how long we have until the next timeout.
      
      2. Start using a blocking poll for events, so I can sleep for long periods
      of time instead of having to wake up at least once a second to check for
      timeouts and events. Will set the block timeout for the shortest of: the
      time to send out the next batch of queued emails, the next time a timeout
      may occur, or when there are no mails waiting and no timeouts possible, 10
      minutes. Comes back as soon as an event comes in.
      
      3. Given the above two items, we no longer need a sleep(1) in our main
      loop.
      
      One small glitch is in the progress of being fixed. When using blocking
      polls, things hang when trying to unregister from the event system. Not a
      big deal, just ^C twice to kill it. (May cause it to need two SIGUSR1's
      to get it to restart, too.)
      
      In the next update, look for:
       - Really take action on timeouts.
         - keep track of how many times we've retried, and notify if something
           may be wrong with the node.
         - Find out policy on taking action with timeouts.
           - Do it if the expt is in transition or the node is free
           - Probably don't touch if the expt is established.
           - Maybe? in active expt, send (good) email to expt owner on timeouts
      
      Related "coming soon" items:
      os_load/os_setup etc.:
       - Add the waitforstate stuff we've talked about
       - make os_load/os_setup use it
      b438d5f5
    • Mac Newbold's avatar
      Add TimeoutQueue.pm - an implementation of a priority queue, customized to · 6c10de1a
      Mac Newbold authored
      be quick and efficient for the types of operations that stated needs to
      make with its timeout queue. But still pretty general, I think.
      6c10de1a