1. 31 May, 2005 1 commit
  2. 04 Nov, 2003 1 commit
  3. 18 Sep, 2003 1 commit
  4. 06 Aug, 2003 1 commit
    • Leigh B. Stoller's avatar
      Clean up temporary files used in modify. The temp dirs were being · 05bd80ff
      Leigh B. Stoller authored
      created in /tmp and left behind. I've moved them to the expwork
      directory instead, and added a routine in the library to clear them
      out.
      
      Clear out the nsfile (stored in /tmp) used in modify. The web page was
      creating a temp file, but never removing it. swapexp now copies the
      nsfile in so that the web page can remove the temporary after the
      script exits. The temp is placed in the expwork directory as well, but
      left behind for debugging.
      
      When swapmod fails, send along the nsfile in the email message.
      05bd80ff
  5. 05 Jun, 2003 1 commit
    • Leigh B. Stoller's avatar
      Add roll of the slowqueries log. · 9d416c02
      Leigh B. Stoller authored
      Add commented out find -delete command to remove all mysql logs older
      than 35 days.  I just run it by hand at the moment, but I'll turn it
      on at some point.
      9d416c02
  6. 25 Oct, 2002 1 commit
  7. 04 Jul, 2002 1 commit
  8. 12 Feb, 2002 1 commit
  9. 11 Feb, 2002 1 commit
    • Leigh B. Stoller's avatar
      Changes to how the backup files are named and saved. The existing · b31fdcdc
      Leigh B. Stoller authored
      naming scheme was not very intuitive and the names sucked. Also, I
      want to increase the frequency with which we run the backups, and I
      want to implement an automated roll so that we only keep about a
      months worth of history around.
      
      Anyway, the new approach is to open up the index file and see what the
      name of the current update file is. It has a numeric extension. Rename
      the base log to base.XXX, and then snapshot the DB into backup.XXX So,
      the combination of update.XXX and base.XXX is the DB history since the
      last time the script was run. The file backup.XXX corresponds to the
      DB at this point in time.
      
      To restore (or track the changes of) a DB, simply take backup.XXX and
      apply the changes that are stored in update.XXX+1 (which are the changes
      made since backup.XXX was made). This should give you a DB that is the
      same as backup.XXX+1. You can go back further, and just apply all the
      subsequent update.XXX files.
      b31fdcdc
  10. 06 Dec, 2001 2 commits
  11. 21 Feb, 2001 1 commit
  12. 16 Jan, 2001 1 commit
  13. 08 Jan, 2001 1 commit