sinfo 0.0.19

sinfo is a system to distribute system information of every host on your local network. The sinfo-system is split into two parts. A demon and a user program.
1. The demon (sinfod) distributes system information using UDP broadcasts on the local network. Each demon will also receive UDP broadcasts of all other demons and manage a list of the most recent informations.
2. The user program (sinfo) connects to the demon via the local loop-back interface and displays the up to date informations using the ncurses library.
This scheme has the advantage that it produces minimal network load. If each node broadcasts its information in a cooperative manner, the network load is O(N), where N is the number of nodes in your network.
Other systems to monitor your cluster load (e.g. rup(1) ) are using a polling scheme where every node has to ask every other node for the system information: In that case the network load is O(N**2).
The Informations broadcasted include:
- The number of CPUs and their speed.
- The network node hostname, the hardware type, the host processor type, the operating system name, the operating system release, the operating system version. Everything uname provides.
- The uptime of the system.
- The load average.
- The current load - split by user, nice, system and idle times.
- The memory usage of the RAM and the swap space.
- The network traffic send and received by the network card.
- Informations of the TOP-5 processes.
Installation:
The `configure shell script attempts to guess correct values for various system-dependent variables used during compilation.
It uses those values to create a `Makefile in each directory of the package. It may also create one or more `.h files containing system-dependent definitions.
Finally, it creates a shell script `config.status that you can run in the future to recreate the current configuration, a file `config.cache that saves the results of its tests to speed up
reconfiguring, and a file `config.log containing compiler output (useful mainly for debugging `configure).
If you need to do unusual things to compile the package, please try to figure out how `configure could check whether to do them, and mail diffs or instructions to the address given in the `README so they can be considered for the next release.
If at some point `config.cache contains results you dont want to keep, you may remove or edit it.
The file `configure.in is used to create `configure by a program called `autoconf. You only need `configure.in if you want to change it or regenerate `configure using a newer version of `autoconf.
The simplest way to compile this package is:
1. `cd to the directory containing the packages source code and type `./configure to configure the package for your system.
If youre using `csh on an old version of System V, you might need to type `sh ./configure instead to prevent `csh from trying to execute `configure itself.
Running `configure takes awhile. While running, it prints some messages telling which features it is checking for.
2. Type `make to compile the package.
3. Optionally, type `make check to run any self-tests that come with the package.
4. Type `make install to install the programs and any data files and documentation.
5. You can remove the program binaries and object files from the source code directory by typing `make clean. To also remove the files that `configure created (so you can compile the package for a different kind of computer), type `make distclean.
There is also a `make maintainer-clean target, but that is intended mainly for the packages developers. If you use it, you may have to get all sorts of other programs in order to regenerate files that came with the distribution.
Enhancements:
- fixed FreeBSD 5.3 compilation, tnx S.Buys
- added --help option to sindo and sinfod