Future of KSysguard - removing remote monitoring
toddrme2178 at gmail.com
Thu Mar 10 15:30:36 GMT 2011
On Thu, Mar 10, 2011 at 10:18 AM, John Tapsell <johnflux at gmail.com> wrote:
> On 10 March 2011 14:43, Cristian Tibirna <tibirna at kde.org> wrote:
>> On March 8, 2011, John Tapsell wrote:
>>> Hi all,
>>> For the past 13 years or so, ksysguard has been in KDE under various
>>> names. Right from the beginning it was designed to monitor remote
>>> systems as well as local ones.
>> John, thanks a lot for taking care of ksysguard. I consider it one of the best
>> applications of the KDE basic workspace. I push it energetically on all sys-
>> admins I find (and usually they're easily convinced).
>> I believe the most important feature of ksysguard is its remote capability. I
>> must acknowledge that I know very little of the mechanics of this feature (yet
>> I know it is developed in-house, since at the time (long ago...), Chris
>> Schlaeger didn't really have much choice in terms of monitoring libraries).
>> I dare to ask you consider to not remove this feature. Perhaps your
>> observation is rather an occasion to look at some redesign (and reuse of
>> better (?) technologies in remote monitoring).
> Thanks - you guys have already changed my mind :-)
It is good it is not going to be removed, but it does sound like there
are problems with the protocol being used that makes the program
difficult to develop.
Could that situation be improved without removing the functionality?
More information about the kde-core-devel