TyopoytaORvelo System Monitor is a desktop system monitor software that keeps track of computer performance and sits unobtrusively in a corner of the screen.
TyopoytaORvelo System Monitor is a system monitor for Linux that can sit in the corner of your desktop. It has the ability to render itself on the root window or to its own transparent window with special eyecandy. This software is capable of showing various system information such as kernel version, uptime, network interface information, memory and swap usage, hostname, machine, i686, and system name, Linux. It can even display temperatures from i2c-sensors.
In terms of installation, the `configure' shell script is used to guess correct values for various system-dependent variables during compilation. The script uses these values to create a `Makefile' in each directory of the package including one or more `.h' files that contain system-dependent definitions. Furthermore, it creates a shell script `config.status' for future configuration, a file `config.cache' to speed up reconfiguring, and a file `config.log' containing compiler output (useful mainly for debugging `configure').
If there's a need to do unusual things to compile the package, `configure' can check whether to do them. Diffs or instructions may be mailed to the address given in the `README' so that they can be considered for the next release. If at some point `config.cache' contains undesired results, it can be removed or edited. Additionally, the file `configure.in' is used to create `configure' by a program called `autoconf.'
To compile this package, a simple five-step process can be done. First is to `cd' to the directory containing the package's source code and type `./configure' to configure the package for your system. If you're 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. Second is to type `make' to compile the package; third is to optionally type `make check' to run any self-tests that come with the package. Fourth is to type `make install' to install the programs and any data files and documentation. Lastly, you can remove the program binaries and object files from the source code directory by typing `make clean.' It is also worth noting that a `make distclean' command can remove the files that `configure' created to allow one to compile the package for a different kind of computer. Developers can use a `make maintainer-clean' target for maintenance purposes.
In terms of installation, the `configure' shell script is used to guess correct values for various system-dependent variables during compilation. The script uses these values to create a `Makefile' in each directory of the package including one or more `.h' files that contain system-dependent definitions. Furthermore, it creates a shell script `config.status' for future configuration, a file `config.cache' to speed up reconfiguring, and a file `config.log' containing compiler output (useful mainly for debugging `configure').
If there's a need to do unusual things to compile the package, `configure' can check whether to do them. Diffs or instructions may be mailed to the address given in the `README' so that they can be considered for the next release. If at some point `config.cache' contains undesired results, it can be removed or edited. Additionally, the file `configure.in' is used to create `configure' by a program called `autoconf.'
To compile this package, a simple five-step process can be done. First is to `cd' to the directory containing the package's source code and type `./configure' to configure the package for your system. If you're 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. Second is to type `make' to compile the package; third is to optionally type `make check' to run any self-tests that come with the package. Fourth is to type `make install' to install the programs and any data files and documentation. Lastly, you can remove the program binaries and object files from the source code directory by typing `make clean.' It is also worth noting that a `make distclean' command can remove the files that `configure' created to allow one to compile the package for a different kind of computer. Developers can use a `make maintainer-clean' target for maintenance purposes.
What's New
Version 0.18: N/A