
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:

 - Add Client tries to start the client.  Furthermore, sh cannot be
   persuaded to stop pinging the thing when it doesn't start..

 - automake/autoconf are genning gmake-only makefiles..  can this be
   fixed?
 
 - 'Start' sets state to 'Working' a bit prematurely, methinks.  Would be
   better if it only got set when we get 'ok' or 'active' back in shnet.
   May apply to other states as well.

 - 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.

