Factoring out standard system information

Richard Moore richmoore44 at gmail.com
Fri Dec 30 12:04:22 GMT 2005

On 12/30/05, Adriaan de Groot <groot at kde.org> wrote:
> There's a couple of non-portable system things that are really popular to
> know
> for KDE applications. These are CPU information (load; percentage time
> idle,
> interrupt, user, etc.), swap and RAM information (free and used). Reading
> these data is a pain in the ass, and it's implemented who knows how many
> times across the KDE codebase -- superkaramba, ksysguard and the just
> discovered (and hopelessly buggy) ktimemon come to mind. I think SK has
> the

Also in kasbar and kst IIRC.

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

I think that's a great idea.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20051230/356a1e8c/attachment.htm>

More information about the kde-core-devel mailing list