Free load software for linux

heatload is a tool for Linux which plots the CPU load against the CPU temperature as measured by the ACPI subsystem.

Installation:

As this package is made with the GNU autotools you should run ./configure inside the distribution directory for configuring the source tree. After that you should run make for compilation and make install (as root) for installation of heatload.

dgnetload is a distributed network load meter and control.
This is a network load meter, much like "xisdnload" from the isdn4linux package, but it works in a distributed setup. It consists of two parts:
- an agent program (devstata) runs on the machine with the interface to be monitored and periodically sends status info over the network
- a display program (gnetload) collects and displays this info.
Both can run on the same machine, but they can also be used to report the state of a dedicated router on another workstation machine.

loadwatch project allows a single child process to run only when the load on a machine is within certain bounds. When the machines load passes the high load mark, then the child process is stopped.

The process is only restarted when the machines load drops below the low load mark. The load is checked at a user definable interval. loadwatch is distributed under the GNU GPL.

Usage:

loadwatch [-d < time>] [-h < load>] [-l < load>] [-n < copies] [-p < pid>] [-- < command>]
-d < int> load sampling interval (10 seconds)
-h < float> high load mark (1.25)
-l < float> low load mark (0.25)
-n < copies> number of children to fork (1)
-u < filename> file that will be used to externally control a
loadwatch process.
-p < pid> pid of process to control (loadwatch will actually
send signals to the group containing this pid)
NOTE: -p and < command> are mutually exclusive, but one has to be
specified.

Example:

loadwatch -d 10 -h 1.25 -l .25 -- ./rc5des

which means: check the load every 10 seconds, stop rc5des when the load is
greater than 1.25 and restart rc5des when the load drops to .25.

lw-ctl < filename> < cmd>
< filename> is the control file, this corresponds to a unix domain
socket.
< cmd> is the command to send to the loadwatch process.
RUN -> put loadwatch into RUN mode, that is the child process
runs regardless of the load.
STOP -> put loadwatch into STOP mode, that is, the child
process will not run regardless of the load.
WATCH -> WATCH mode, the normal load watching mode.

Example:

lw-ctl ./fooey RUN

Causes the loadwatch process (if it was started with "-u ./fooey") to go
into RUN mode. you could put lw-ctl in a cron job that runs in the
morning to put the job in STOP mode and then again in the evening to put
the job back into WATCH mode.

The children which loadwatch forks are all part of the same process group.
loadwatch stops and starts the processes by signalling the process
group with SIGSTOP and SIGCONT respectively.

Send suggestions and bug reports to . if you do anything
interesting with loadwatch, let me know. i use it for controlling the
distributed.net clients, but i figure itd be good to control thinks like
crack as well.

Prima::image-load is a Perl module using image subsystem.

Simple loading

Simplest case, loading a single image would look like:

my $x = Prima::Image-> load( filename.duf);
die "$@" unless $x;

Image functions can work being either invoked from package, or from existing Prima::Image object, in latter case the caller object itself is changing. The code above could be also written as

my $x = Prima::Image-> create;
die "$@" unless $x-> load( filename.duf);

In both cases $x contains image data upon success. Error is returned into $@ variable ( see perldoc perlvar for more info).

Crossroads is a load balance and failover utility for TCP-based services.
Crossroads Load Balancer is a daemon program running in userspace and features extensive configurability, polling of backends using "wakeup calls", detailed status reporting, "hooks" for special actions when backend calls fail, and more.
It is service-independent; it is usable for HTTP(S), SSH, SMTP, DNS, etc.
Crossroads is a daemon that basically accepts TCP connections at preconfigured ports, and given a list of back ends distributes each incoming connection, so that a client process is served.
Additionally, crossroads maintains an internal administration of the back end connectivity: if a back end isnt usable, then the client request is handled using another back end. Crossroads will then periodically check whether a previously not usable back end has come to life yet. Also, crossroads can select back ends by estimating the load, so that balancing is achieved.
Using this approach, crossroads serves as load balancer and fail over utility. Crossroads will very likely not be as reliable as hardware based balancers, since it always will require a server to run on. This server, in turn, may become a new Single Point of Failure (SPOS). However, in situations where cost efficiency is an issue, crossroads may be a good choice.
Furthermore, crossroads can be deployed in situations where a hardware based balancing already exists and augmenting service reliability is needed. Or, crossroads may be run off a diskless system, which again improves reliability of the underlying hardware.
This document describes how to use crossroads, how to configure it in order to increase the reliability of your systems, and how to compile the program from its sources. This document is also available in PDF format.
Usage:
Crossroads is started from the commandline, and highly depends on /etc/crossroads.conf (the default configuration file). It supports a number of flags (e.g., to overrule the location of the configuration file). The actual usage information is always obtained by typing crossroads without any arguments. Crossroads then displays the allowed arguments.
This section shows the basic usage.
- crossroads start and crossroads stop are typical actions that are run from system startup scripts. The meaning is self-explanatory.
- crossroad status reports on each running service. Per service, the state of each back end is reported.
- crossroads tell service backend state is a command line way of telling crossroads that a given back end, of a given service, is in a given state. Normally crossroads maintains state information itself, but by using crossroads tell, a back end can be e.g. taken off line for servicing.
- crossroads services reports on the configured services. In contrast to crossroads status, this option only shows whats configured -- not whats up and running. Therefore, crossroads services doesnt report on back end states.
- crossroads sampleconf shows a sample configuration on screen. A good way of quicky viewing the configuration file syntax, or of getting a start for your own configuration /etc/crossroads.conf.

gnetload network load meter project is a network and ISDN load meter that is similar to xisdnload, but works in a distributed environment.
It includes an agent (devstata) that runs on machines with interfaces to be monitored and periodically sends status information over the network. A display program (gnetload) collects and displays the data.
Both can be run on the same machine, or be used to report on the state of a dedicated router on another machine. Using multicast or broadcast addresses, data can be fed to more than one instance of gnetload. A menu for taking network interfaces up and down is also provided.
Usage: ./gnetload [-I] [-t tickscale] [-g geometry] [-d] [ip]:port
Enhancements:
- The config script was updated to build with GTK2 and GCONF2 where available.
- There are no other code changes.

The Bubbling Load Monitor (or "Bubblemon" for short) is a system CPU and memory load monitor.
It displays something that looks like a vial containing water. The water level indicates how much memory is in use. The color of the liquid indicates how much swap space is used (watery blue means none and angry red means all).
The system CPU load is indicated by bubbles floating up through the liquid; lots of bubbles means high CPU load. If you have unread mail, a message in a bottle falls into the water.
Enhancements:
- The word "bytes" may now be translated.
- The French translation was updated.
- The maintainers e-mail address was updated.