|
The command line interface (CLI) version of Monitor provides the same monitoring functionality as the graphical version. The CLI utility can monitor the following:
For conceptual information about monitoring, whether with the CLI or GUI version of the utility, see Monitor Utility Overview .
CLI Monitor runs on the Windows and Linux platforms supported by Pervasive PSQL v9 Service Pack 2.
On Windows, the executable program name is bmon.bat and is located, by default, in the PVSW\bin directory.
On Linux, the executable program name is bmon and is located, by default, in the /usr/local/psql/bin directory. Certain requirements must be met before you can run bmon on Linux. These requirements are the same as for another Java utility, bcfg. See Table 4-1, Requirements for Running bcfg on Linux, and Table 4-2, Troubleshooting Guide for Running bcfg on Linux, .
Bmon requires a configuration file to provide settings for the utility. Pervasive PSQL v9 Service Pack 2 provides a sample configuration file named monconfig.txt. It is located, by default, in the "bin" directory of the Pervasive PSQL installation directory.
Refer to the comments in the sample configuration file for the settings that you can configure.
Output from Bmon can be directed to the console, a log file, or both. An application could, for example, check for a particular condition from the console or in a log file, then take appropriate action.
The configuration file specifies where to direct the output.
The runonce parameter is optional. If omitted, the utility executes the settings in the configuration file, then pauses for the duration of the refresh rate. During the pause, you can send the utility a valid keyboard key response as shown below. If the refresh rate is set to zero, the utility pauses indefinitely until it receives a valid keyboard key response.
The refreshrate setting in the configuration file specifies how many seconds to pause.
|
Chapter contents
Prev topic: Monitoring SQL Interface Resources
|