[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Fwd: [PATCH] ksysguard support for hddtemp and nvidia sensors
From:       Maurizio Monge <maurizio.monge () gmail ! com>
Date:       2005-01-29 16:37:24
Message-ID: e4c51935050129083717e7e895 () mail ! gmail ! com
[Download RAW message or body]

Resending...
is there any reason my patch was not merged or was it just ignored?
I don't really hope to see it in kde 3.4 (even if i would like it), but jut
tell me if there is anything wrong :-)

Thanx.


---------- Forwarded message ----------
From: Maurizio Monge <maurizio.monge@gmail.com>
Date: Thu, 20 Jan 2005 00:15:29 +0100
Subject: [PATCH] ksysguard support for hddtemp and nvidia sensors
To: cs@kde.org, kde-devel@mail.kde.org


Hello,
i am attaching a patch (to be applied in the
ksysguard dir with -p1) that adds support for:

1)hddtemp, it just connects to the port where hddtemp
is usually run as daemon (7634), to use it i run for
instance

hddtemp -w -d /dev/hda /dev/hdb /dev/hdc

at boot.
Todo: if ksysguardd is run as root it should
able to read smart sensors also without hddtemp
running as daemon.

2)nvidia (proprietary :-( ) sensors, it is implemented
exaclty as in the nvidia-settings tool (the tool itself is
GPL). I have copied from nvidia-settings the directory
"libXNVCrtl", and what it basically does is connecting
to the Xserver and ask for sensors status.
Caveats: since the sensors are read by connecting the
the xserver ksysguardd has to link to the X11 and Xext
libraries. If ksysguardd is also run as daemon (with DISPLAY
not set) this sensor will not work. Anyway i think that in most
distros ksysguardd is run by ksysguard as user so it will
usually works. Nvidia support is disabled if /dev/nvidiactl is
not present. What is your opinion?

Ciao
Maurizio

PS: i am not subscribed to kde-devel so please CC any answer to

maurizio.monge
@gmail.com

["ksysguard+nv+hdd.bz2" (application/octet-stream)]

>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<


[prev in list] [next in list] [prev in thread] [next in thread]