Make the connection to ksysguardd more robust.
This should fix quite a few bugs. For example if you "killall ksysguardd", it barely even blinks now. As opposed to screwing it up for now-and-forever as it did :(

In particular:
* Automatic reconnection to the host if disconnected
* If the connection dropped then there might be some incomplete data. Deal with this cleanly.
* If the configuration file is corrupted and doesn't have a <host> (easy state to get into :( ) then assume all "localhost" connections go via ksysguardd daemon