Upstream software project

gkrellm

Files needed for gkrellm2 development

About gkrellm

Files needed for gkrellm2 development

This project links 8 native package records across 2 recorded operating-system releases. Compare the retained versions and architectures below, then open the package for your own release.

These are catalog observations, not a guarantee of installation, compatibility, or upstream support.

Project pictures and package coverage

openSUSE Leap 15.6: 4 package records; openSUSE Leap 16.0: 4 package records. Catalog coverage diagram, not an application screenshot.gkrellm: recorded package coverageopenSUSE Leap 15.64 recordsopenSUSE Leap 16.04 records
OpenFactory diagram of linked package records. It is not an application screenshot.

Project identity

Project
gkrellm
Publisher
Not authoritatively mapped
Native package records
8
Operating systems
opensuse-leap-15-6, opensuse-leap-16-0
License expression
GPL-3.0-or-later
Source repository
Not reported

Source-reported description

The fullest retained description is shown with its source. Distribution packaging descriptions may include downstream details.

With a single process, GKrellM manages multiple stacked monitors and supports applying themes to match the monitors appearance to your window manager, Gtk, or any other theme. * SMP CPU, Disk, Proc, and active net interface monitors with LEDs. * Internet monitor that displays current and charts historical port hits. * Memory and swap space usage meters and a system uptime monitor. * File system meters show capacity and free space and can mount and umount. * A mailbox monitor that can launch a mail reader and fetch remote mail. * Clock, calendar, and hostname display. * APM laptop battery monitor. * CPU and motherboard temperature display if lm_sensors modules are installed. * Multiple monitors managed by a single process to reduce system load. * PPP on and off button that can execute your PPP scripts. * Charts are autoscaling with configurable grid line resolution. * Separate colors for "in" and "out" data. The in color is used for CPU user time, disk read, forks, and net receive data. The out color is used for CPU sys time, disk write, load, and net transmit data. * A different theme can be created with the GIMP.

Description source

Packages by operating system

Compare recorded versions, then open a package for dependency, file, checksum, and repository evidence. Version strings are distribution-specific, not a ranking of newer software.

openSUSE Leap 15.6

  1. Package gkrellm

    leap-15.6 (openSUSE Leap 15.6) (System/Monitoring): Manages Multiple Stacked Monitors

    2.3.11-bp156.3.8: aarch64 ppc64le x86_64

    Source: gkrellm

  2. Package gkrellmd

    leap-15.6 (openSUSE Leap 15.6) (System/Monitoring): Multiple Stacked Monitors daemon

    2.3.11-bp156.3.8: aarch64 ppc64le x86_64

    Source: gkrellm

  3. Package gkrellm-devel

    leap-15.6 (openSUSE Leap 15.6) (Development/Sources): Files needed for gkrellm2 development

    2.3.11-bp156.3.8: aarch64 ppc64le x86_64

    Source: gkrellm

  4. Package gkrellm-lang

    leap-15.6 (openSUSE Leap 15.6) (System/Localization): Translations for package gkrellm

    2.3.11-bp156.3.8: noarch

    Source: gkrellm

openSUSE Leap 16.0

  1. Package gkrellm

    leap-16.0 (openSUSE Leap 16.0) (System/Monitoring): Manages Multiple Stacked Monitors

    2.3.11-bp160.1.13: aarch64 ppc64le x86_64

    Source: gkrellm

  2. Package gkrellmd

    leap-16.0 (openSUSE Leap 16.0) (System/Monitoring): Multiple Stacked Monitors daemon

    2.3.11-bp160.1.13: aarch64 ppc64le x86_64

    Source: gkrellm

  3. Package gkrellm-devel

    leap-16.0 (openSUSE Leap 16.0) (Development/Sources): Files needed for gkrellm2 development

    2.3.11-bp160.1.13: aarch64 ppc64le x86_64

    Source: gkrellm

  4. Package gkrellm-lang

    leap-16.0 (openSUSE Leap 16.0) (System/Localization): Translations for package gkrellm

    2.3.11-bp160.1.13: noarch

    Source: gkrellm

Project resources and further reading

Mapping provenance

Only source-backed identity signals create public cross-OS links. A reviewer can later approve or dispute an inferred relationship without rewriting native package history.

No field-level source record is published yet.