Bug 96333 - ksysguardd: remote host connection instructions poorly explained
Summary: ksysguardd: remote host connection instructions poorly explained
Status: RESOLVED FIXED
Alias: None
Product: docs.kde.org
Classification: Websites
Component: Missing Content (show other bugs)
Version: unspecified
Platform: Debian testing Linux
: NOR normal
Target Milestone: ---
Assignee: Documentation Editorial Team
URL:
Keywords:
: 96593 (view as bug list)
Depends on:
Blocks:
 
Reported: 2005-01-05 01:06 UTC by Sean T. Evans
Modified: 2011-12-08 10:25 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Sean T. Evans 2005-01-05 01:06:57 UTC
Version:            (using KDE KDE 3.3.1)
Installed from:    Debian testing/unstable Packages
Compiler:           Installed from Debian-Unstable binaries.
OS:                Linux

In trying to setup KDE System Guard to monitor another machine on my local network, I have been unable to connect. The instructions in the documentation are very sparse.
From documentation: 
"The easiest way to check this is to type ssh remotehost ksysguardd in a shell. If you are greeted by ksysguardd you can type quit and everything is in order."
I am greeted by a password request by ssh, which is not mentioned. Once I give this password, I am greeted by ksysguardd> prompt. I then type quit and am exited.

If I then go to the ksysguard app, and attempt to connect to the remote host, The name of the remotehost displays, but with no sensors. After about 5 seconds, I get a message that   "Connection to remotehost has been lost" no other errors or explaination, and no troubleshooting information seems to be available in the documentation.
Comment 1 Virgil Nisly 2005-01-08 20:23:20 UTC
*** Bug 96593 has been marked as a duplicate of this bug. ***
Comment 2 T.C. Hollingsworth 2011-12-08 10:25:17 UTC
This documentation seems to have been significantly improved in the intervening years.  Please let us know if there's anything else we can do.