A software tool that interprets a rule-based programming language expressed in a declarative syntax.
NodeBrain is an exceptional rule-based language interpreter that is tailored for creating event and state-monitoring applications. It is not just an event correlation engine but a complete solution that supports interfacing with other monitoring components to make rule-based decisions. The software uses authenticated and encrypted peer-to-peer communication over TCP/IP to generate event streams and perform rule administration. It also includes encrypted file transfers, store-and-forward message queues, and remote command execution.
The software installation process is streamlined and simplified using the configure shell script. This script attempts to guess the appropriate values for various system-dependent variables used during compilation. It creates a Makefile in each directory of the package using the values obtained. As a result, this approach guarantees proper configuration and eliminates potential issues that may occur regarding the package installation.
The installation process creates a shell script called config.status, which can be used to recreate the present configuration whenever necessary. It also generates a config.cache file that saves the results of its tests to quicken the reconfiguration process. Plus, it develops a file named config.log that contains compiler output useful mainly for debugging configure. If there is any need to do unusual things to compile the package, configure can check whether to execute them. Thus it would be best if you mailed diffs or instructions to the given address in the README, which can be considered for the next release.
If the config.cache contains results you do not want to keep, you can choose to delete or edit it to your preference. The software creates the configure.in file, which is used to generate configure by a program known as autoconf. You might only require configure.in if you intend to change it or regenerate configure utilizing a newer version of autoconf.
The quickest way to compile this package is to change directory to the package source code directory and type './configure' to configure the package for your system. However, if you are using csh on an older version of System V, you may need to type 'sh./configure' to prevent csh from trying to execute configure itself. The configure process can take a while to complete, and during execution, it prints messages defining the features it is checking.
After the configure process, type 'make' to compile the package. If the package contains any self-tests, they will run automatically after typing 'make check.' Again, type 'make install' to deploy any data files, documentation, and programs. If you ever need to remove the program binaries and object files from the source code directory, type 'make clean.' Furthermore, if you want to remove the files configure created to compile the package appropriately for a different kind of computer, type 'make distclean.' However, developers designed the 'make maintainer-clean' to target the package's developers. It regenerates files that came with the distribution, and you may require all sorts of other programs to execute it.
The software installation process is streamlined and simplified using the configure shell script. This script attempts to guess the appropriate values for various system-dependent variables used during compilation. It creates a Makefile in each directory of the package using the values obtained. As a result, this approach guarantees proper configuration and eliminates potential issues that may occur regarding the package installation.
The installation process creates a shell script called config.status, which can be used to recreate the present configuration whenever necessary. It also generates a config.cache file that saves the results of its tests to quicken the reconfiguration process. Plus, it develops a file named config.log that contains compiler output useful mainly for debugging configure. If there is any need to do unusual things to compile the package, configure can check whether to execute them. Thus it would be best if you mailed diffs or instructions to the given address in the README, which can be considered for the next release.
If the config.cache contains results you do not want to keep, you can choose to delete or edit it to your preference. The software creates the configure.in file, which is used to generate configure by a program known as autoconf. You might only require configure.in if you intend to change it or regenerate configure utilizing a newer version of autoconf.
The quickest way to compile this package is to change directory to the package source code directory and type './configure' to configure the package for your system. However, if you are using csh on an older version of System V, you may need to type 'sh./configure' to prevent csh from trying to execute configure itself. The configure process can take a while to complete, and during execution, it prints messages defining the features it is checking.
After the configure process, type 'make' to compile the package. If the package contains any self-tests, they will run automatically after typing 'make check.' Again, type 'make install' to deploy any data files, documentation, and programs. If you ever need to remove the program binaries and object files from the source code directory, type 'make clean.' Furthermore, if you want to remove the files configure created to compile the package appropriately for a different kind of computer, type 'make distclean.' However, developers designed the 'make maintainer-clean' to target the package's developers. It regenerates files that came with the distribution, and you may require all sorts of other programs to execute it.
What's New
Version 0.6.5: N/A