1. 07 Jul, 2002 1 commit
  2. 16 Apr, 2002 1 commit
  3. 15 Apr, 2002 1 commit
  4. 15 Mar, 2002 1 commit
  5. 07 Mar, 2002 1 commit
  6. 08 Jan, 2002 1 commit
    • Leigh B. Stoller's avatar
      Fix up genlastlog to avoid Y2K like problems. Basically, syslog does · cb096341
      Leigh B. 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
  7. 30 Oct, 2001 1 commit
  8. 29 Oct, 2001 1 commit
    • Leigh B. Stoller's avatar
      A bunch of lastlogin changes! The user and experiment information · 4658545e
      Leigh B. 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