Bug 193845

Summary:	ksysguardd would make a nice service
Product:	[Fedora] Fedora	Reporter:	Greg Martyn <greg.martyn>
Component:	kdebase	Assignee:	Than Ngo <than>
Status:	CLOSED WONTFIX	QA Contact:	Ben Levenson <benl>
Severity:	low	Docs Contact:
Priority:	medium
Version:	5	CC:	laurent.rineau__fedora
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
URL:	http://developer.kde.org/~binner/distributor-patches/SUSE/10.1/kdebase3-3.5.1-69/ksysguardd.init
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2008-03-11 23:32:06 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Greg Martyn 2006-06-02 05:01:40 UTC

SUSE lets you start ksysguardd as a init.d process. It would be nice if Fedora
supported that too.

KSysGuardd is a daemon that lets ksysguard (the gui) monitor remote computers.

A patch is available:
http://developer.kde.org/~binner/distributor-patches/SUSE/10.1/kdebase3-3.5.1-69/ksysguardd.init


Thanks.

Comment 1 Laurent Rineau 2008-03-11 22:34:57 UTC

ksysguard can monitor remote computer through ssh, launching ksysguardd on the 
remote machine if needed. What are the advantages to have ksysguardd launched 
by init? Is not there any security issue?!

Comment 2 Greg Martyn 2008-03-11 23:32:06 UTC

The sensitive parts of ksysguardd are disabled when run as a daemon (the -d
switch), but you're right; I can't think of any advantage to using the daemon
over ssh=>ksysguardd