GKrellM
GKrellM is a GTK-based stacked monitor program that charts SMP CPUs, disks, load, active net interfaces, and internet connections. There are also builtin monitors for memory and swap, file systems with mount/umount feature, mailbox checking including POP3 and IMAP, clock/calendar, laptop battery, sensors (temperatures, voltages, and fans), and uptime. It has LEDs for the net monitors and an on/off button and online timer for PPP. There is a GUI popup for configuration, plugin extensions can be installed, and many themes are available. It also features a client/server monitoring capability.
| Tags | Monitoring Networking |
|---|---|
| Licenses | GPL |
| Operating Systems | POSIX BSD FreeBSD NetBSD OpenBSD Linux Solaris |
| Implementation | C |
Recent releases
- 05 Jan 2009 11:53
Changes: Error logging was added, which allows logging to a file or stdout. Additionally, gkrellmd can now log to syslog. Mail authentication is now (optionally) done via libntlm. Clock and calendar strings are now parsed by honoring the current system locale. The Linux sysfs battery interface is now supported and preferred over the deprecated /proc/acpi interface. Support for building on Mac OS X Leopard was added. Various bugs were fixed and translations were updated.
- 10 Dec 2007 05:58
Changes: The Clock/Calendar monitor was rewritten to use user configurable display format strings containing strftime conversion characters and Pango text attribute markup strings. Various bugs were fixed.
- 03 Aug 2007 11:05
Changes: Various bugfixes and updates.
- 05 May 2006 07:35
Changes: This release fixes a segfault which occurred if the user selected the configuration option Builtins-Battery with no batteries present.
- 18 Mar 2006 22:04
Changes: gkrellmd can send a network interface connect time to be displayed on client timer button panels by configuring a net-timer in gkrellmd.conf. Virtual disk (/dev/mdX) stats are not added to the composite disk stats. A compile error related to inet6 was fixed in server/main.c for machines with old libc. gnutls multithread initialization was added to mail.c. While mixing draw_decal_text and decal_scroll_text calls on transparent panels, the text layer pixmap was not cleaned up properly. Updates were made to the German translation.
- All comments
Recent commentsRe: Change update interval of sensors
% Ditto. You can always reparent the whole
> window and embed it into a plasmoid. It
> should be doable just like you can
> swallow it into FvwmButtons in fvwm.
>
> However, I see no advantage in doing so.
> That will be just gkrellm with extra
> fuzziness due the the interaction with
> the container. No advantage and lot of
> potential problems.
Actually it would be great if we could embed the whole window into a plasmoid. Because now the gkrellm window is jsut a normal window and constantly gets in my way. It gains focus periodically, it can't get removed from the pager, I easily close it while trying to close other windows with keyboard shortcuts (if it's visible and has focus, nothing indicates this) etc.
Re: Change update interval of sensors
> That would probably be a tough thing as
> gkrellm is based on Gtk+ and porting it
> to Qt/KDE basically means rewriting it.
> The only thing I can imagine right now
> (as an ex-KDE user/developer) would be
> to embed the whole gkrellm window in a
> small plasmoid-app that allows embedding
> any borderless application-window. I
> don't really know anything about newer
> KDE4 APIs though.
>
Ditto. You can always reparent the whole window and embed it into a plasmoid. It should be doable just like you can swallow it into FvwmButtons in fvwm.
However, I see no advantage in doing so. That will be just gkrellm with extra fuzziness due the the interaction with the container. No advantage and lot of potential problems.
For this to take advantage of the plasma thing the whole app needs to be ported, as you said. I have no experience with plasma concretely, though qt/kdelibs stuff can be written easily and fast. Unfortunately I know nothing about the gkrellm internals either.
Great program by the way.
Re: Change update interval of sensors
Hey tnx a lot for the info Stefan. Looking forward to update every second or 2. :) I am a crazy gkrellm user, I constantly monitor everything. :) You learn a lot of your machine with that and can easily determine something's wrong when values go outside what you're used to see. :)
As for KDE4, I understand. I am not much a dev guy, but I do know how to test (part of my job). So I will try and start with the easy way, if I succeed. Re-writing will be complex for me, I think I could do some sensors, but certainly not all the options I used and not all the ones available. I'll take your advice and go for it.
tnx!
Re: Change update interval of sensors
> Ok great, tnx for the info! I won't
> spend more time trying to edit that 5
> seconds. :) I'll wait for a newer
> version to have it user editable.
I'll add it to my TODO list, shouldn't be too hard to get this into 2.3.3.
> And hopefully one version to have
> gkrellm as a plasmoid in KDE4. I am
> trying to learn how to port an
> application to plasma, but I believe it
> might not be as easy as I thought for
> gkrellm.
That would probably be a tough thing as gkrellm is based on Gtk+ and porting it to Qt/KDE basically means rewriting it. The only thing I can imagine right now (as an ex-KDE user/developer) would be to embed the whole gkrellm window in a small plasmoid-app that allows embedding any borderless application-window. I don't really know anything about newer KDE4 APIs though.
Re: Change update interval of sensors
>
> % I know the sensors (temps, fans,
> % voltages) update every 5 seconds. How
> % can I change this to a different
> value?
> % I've googled around for hours and
> never
> % found anyone trying to do such a
> thing.
>
>
> It's hardcoded right now and probably
> should be made configurable similar to
> the interval when checking disk-space.
Ok great, tnx for the info! I won't spend more time trying to edit that 5 seconds. :) I'll wait for a newer version to have it user editable.
And hopefully one version to have gkrellm as a plasmoid in KDE4. I am trying to learn how to port an application to plasma, but I believe it might not be as easy as I thought for gkrellm.
Frank