1. 07 Mar, 2003 1 commit
  2. 30 Jan, 2003 1 commit
  3. 07 Jan, 2003 1 commit
  4. 02 Dec, 2002 1 commit
  5. 31 Oct, 2002 1 commit
  6. 06 Sep, 2002 1 commit
  7. 07 Jul, 2002 1 commit
  8. 05 Jul, 2002 2 commits
  9. 04 Jun, 2002 1 commit
  10. 31 May, 2002 1 commit
  11. 17 Apr, 2002 1 commit
  12. 16 Apr, 2002 1 commit
  13. 15 Apr, 2002 2 commits
  14. 15 Mar, 2002 1 commit
  15. 08 Mar, 2002 1 commit
  16. 07 Mar, 2002 1 commit
  17. 12 Feb, 2002 1 commit
  18. 09 Jan, 2002 1 commit
  19. 08 Jan, 2002 1 commit
    • Leigh Stoller's avatar
      Fix up genlastlog to avoid Y2K like problems. Basically, syslog does · cb096341
      Leigh Stoller authored
      not include a year in the output, so I was using the current year to
      init the tm structure. However, the log file could span from the old
      year to the new year, and so all the dates could be wrong. Using Mac's
      suggestion, look at the final time stamp, and if its in the future,
      reset it back one year.
      
      Also add [-a #] option to roll through the specified number of
      rotation files, to make the job of reinitting all the records easier.
      I ran it as "genlastlog -a 7", which makes it process logins.7.gz
      through logins.0.gz, before doing the current log.
      cb096341
  20. 03 Dec, 2001 1 commit
  21. 30 Oct, 2001 1 commit
  22. 29 Oct, 2001 1 commit
    • Leigh Stoller's avatar
      A bunch of lastlogin changes! The user and experiment information · 4658545e
      Leigh Stoller authored
      pages now show the lastlogin info that is gathered from sshd syslog
      reporting to users. That info is parsed by security/genlastlog.c, and
      entered into the DB in the nodeuidlastlogin and uidnodelastlogin
      tables. If not obvious from the names, for each user we want the last time
      they logged in anyplace, and for each node we want the last time anyone
      logged into it. The latter is obviously more useful for scheduling
      purposes. All of the various images have new /etc/syslog.conf files,
      and the 6.2 got new sshd_configs (all cvsup'ed with kill -HUP). There
      is an entry in boss:/etc/crontab and users:/etc/syslog.conf. All of
      this is decribed in greater detail in security/genlastlog.c.
      4658545e
  23. 16 Oct, 2001 1 commit
  24. 15 Oct, 2001 1 commit
    • Leigh Stoller's avatar
      Add node_admin command for users. Simply switches between the normal · 85b512e7
      Leigh Stoller authored
      testbed boot process and the freebsd pxeboot/MFS kernel. I'm hoping
      this will be useful enough for users to load their own disk images,
      but we shall see. Usage is simple:
      
      	/usr/testbed/bin/node_admin on|off pcXXX
      
      The "on" state boots the MFS, and the "off" states sets it back to
      normal.
      85b512e7
  25. 05 Oct, 2001 2 commits
  26. 01 Oct, 2001 2 commits
  27. 21 Sep, 2001 1 commit
  28. 19 Sep, 2001 1 commit
  29. 18 Sep, 2001 1 commit
  30. 01 Aug, 2001 1 commit
    • Leigh Stoller's avatar
      An attempt at making image creation an easy/automatic operation. HA! · 27f26d99
      Leigh Stoller authored
      This uses the pxe booted freebsd kernel and MFS. In addition, I use
      the standard testbed mechanism of specifying a startup command to
      run, which will do the imagezip to NFS mounted /proj/<pid>/.... The
      controlling script on paper sets up the database, reboots the node,
      and then waits for the startstatus to change. Then it resets the DB
      and reboots the node so that it returns back to its normal OS. The
      format of operation is:
      
      	create_image <node> <imageid> <filename>
      
      Node must be under the user's control of course. The filename must
      reside in the node's project (/proj/<pid>/whatever) since thats the
      directory that is mounted by the testbed config software when the
      machine boots. The imageid already exists in the DB, and is used to
      determine what part of the disk to zip up (say, using the slice option
      to the zipper). Since this operation is rather time consuming, it does
      the usual trick of going to background and sending email status later.
      27f26d99
  31. 21 May, 2001 2 commits
  32. 10 May, 2001 1 commit
  33. 20 Apr, 2001 1 commit
  34. 11 Apr, 2001 1 commit
  35. 04 Apr, 2001 1 commit