Oculus is a client-server based software for server monitoring. It allows users to monitor their servers efficiently and easily.
Key features of Oculus include XML configuration files, a plaintext protocol, and plugin support. In addition, the software utilizes /proc to obtain system and process information, making it simple to use the default plugin to obtain data.
As for installation, the `configure' shell script strives to deduce accurate values for various system-dependent variables that come into play during compilation. Once the values are determined, Oculus creates a Makefile in each package directory, along with one or more `.h' files that contain system-dependent definitions. Additionally, Oculus creates a shell script dubbed `config.status' that can be utilized in future to reproduce the current configuration, a file called `config.cache' to store the results of test caching to speed up reconfiguration, and a file named `config.log' that contains compiler output (helpful mainly for debugging `configure').
If you need to perform extraordinary setup procedures to compile the package, we suggest that you investigate how `configure' works to determine whether to apply them or not. You can also mail diffs or instructions to the address specified in the `README' so they can be taken into account for the next software release. If `config.cache' has results you do not intend to keep, you may remove or modify them.
Oculus uses `configure.in' to develop `configure' through a program called `autoconf.' `configure.in' is only necessary if you want to alter it or regenerate `configure' by utilizing a new version of `autoconf.'
Installing Oculus entails several procedures, and the simplest way to accomplish this task is by first `cd' into the directory containing the source code package and running `./configure' to configure the package for your system.
It is worth mentioning that running `configure' takes some time, given that it produces messages detailing the features it is examining. Once completed, type `make' to compile the package, and optionally, you can perform self-tests with `make check.' To install the programs and any data files and documentation, type `make install.'
Finally, you can delete the program binaries and object files from the source code directory by typing `make clean.' Likewise, to remove the files generated by `configure' to build the package for another form of computer, punctuate your command with `make distclean.' The package's developers mostly intend the `make maintainer-clean' target yet, you might have to get various other programs to rebuild reports that came with the distribution.
Version 0.8: N/A