--nextPart3838680.SgItFK68cX
Content-Type: text/plain;
  charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

There's a couple of non-portable system things that are really popular to k=
now=20
for KDE applications. These are CPU information (load; percentage time idle=
,=20
interrupt, user, etc.), swap and RAM information (free and used). Reading=20
these data is a pain in the ass, and it's implemented who knows how many=20
times across the KDE codebase -- superkaramba, ksysguard and the just=20
discovered (and hopelessly buggy) ktimemon come to mind. I think SK has the=
=20
most accurate code - at least it gives me numbers that match what top(1) an=
d=20
swapinfo(8) tell me. KTimeMon has support for OSF but not for FreeBSD, whic=
h=20
is .. uncomfortable and/or weird.

So would it make sense to factor this stuff out and stick it in kdelibs=20
somewhere? ksysinfo or some such -- one central place to query system=20
resource usage, so there's only one place reading /proc/icky/memusage or=20
calling sysctlbyname("hw.memusage") or calling table() or using kvm(4).

How does that square with SK's merger into plasma? The system resource read=
ing=20
is some of the most popular stuff in SK.


=2D-=20
These are your friends - Adem
    GPG: FEA2 A3FE Adriaan de Groot

--nextPart3838680.SgItFK68cX
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (FreeBSD)

iD8DBQBDtJSjdqzuAf6io/4RAiOOAJ9ahqc5XdcB9jN8ujZfVvXSyO+baACghRO6
u0Q5lhOiCT+wYJt2JP+9yLs=
=0dzB
-----END PGP SIGNATURE-----

--nextPart3838680.SgItFK68cX--