Things to do:

- Actually think about doing what I put in this file.

- Handle wtmp corruption. There are numerous reasons for this happening,
  including hard resets which result in lost data that was never written to
  the wtmp file.  I believe that it would be possible to "re-sync" a wtmp
  file rather easily by looking for strings like "LOGIN" or "tty" or "ftp"
  and then backtrack until we reach the bad entry or entries and then remove
  them. Determining at what point wtmp is corrupted, if it really is, could
  be problematic.  Wild changes in time could just be root playing with the
  clock, not true corruption, as someone may have to do when first setting
  up the system when the cmos clock is incorrectly set.

  A separate utility would be required to actually fix wtmp, as several
  options would no doubt be required to control how and in what direction it
  attempts to fix wtmp.  Forget Solaris, it's just broken, and it's going to
  stay that way.

- Add more features!!

