
When reporting a bug, please do your best to describe *everything* about
your setup -- how are you spawning remote processes, what OSes, what 
version of the seti@home client are you using, what you were doing at the 
time the bug occurred, etc..  It will be very appreciated.

Known bugs/issues:

 - parent terminal can get funky with weird client exits; needing 'reset'
   - some seriously freaky keyboard input bugginess when herder gets 
     dropped into the background.  Some keystrokes into the parent term
     get eaten.  Gotta have something to do with my job control changes.

 - the client->died business is goofy.  Too much globalishness.  Fix.

 - When used with GTK 1.2.0 or 1.2.1, the expanded dialog causes a lot of
   strange GtkBlahBlah messages to appear on stdout.  This is a known problem,
   as these two versions of gtk wouldn't let you create a label with a NULL
   string.  They've fixed it in the most up-to-date versions, so I'm calling
   it an old Gtk bug and do not plan to work around it.

