Things to do:

- Try to make a two-pass system over the wtmp file to extract the precise
  starting and ending dates of the wtmp file so that the -s and -e options
  can also apply to users.  It would also just make implementing -s and -e
  cleaner and easier.  Since their could always be wtmp corruption this may
  not be a good idea.  It's been my experiance that poorly administered
  or problematic systems tend to develop problems with wtmp.  If writing
  to wtmp were handled through a daemon like syslogd I suspect there would
  be fewer problems.  The same goes for utmp.

- 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 beleive 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 seperate 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!!

