Recent changes to Overview

Overview modified by Les Peters

Les Peters — Mon, 15 Dec 2014 19:32:24 -0000

--- v3
+++ v4
@@ -14,31 +14,3 @@
 * BSD

 In short, if the operating system can run Perl version 5.004 patch 4 or later, it can run OmniCheck. If someone knows of a system where this assertion fails, please post a message in OmniCheck's Help forum the project so I can fix whatever is going wrong.
-
-### Changes from last version (6.1.1) ###
-
-Exec actions now support use of FILENAME substitution
-
-## Installation ##
-
-### Management via iterative process (cron) ###
-
-1. Create installation directory (if not already present) referred hereafter as {install_dir}
-
-

mkdir /opt/omnicheck # or wherever you wish

- -2. Create logs directory (if being used) - -

mkdir /opt/omnicheck/logs # or wherever you wish

- -3. Create configuration file or copy one of the samples from this site (see Configuration for details) - -

cd {install_dir}; vi configfile

- -4. Create rule file(s) in the directory noted as 'home' in the configuration file (see Rule files for details) - -

vi {install_dir}/rules.{nodename}

- -5. Begin monitoring in the selected tool (cron) - -

/usr/local/bin/perl {install_dir}/omnicheck -F {install_dir}/configfile

Overview modified by Les Peters

Les Peters — Sat, 13 Dec 2014 21:27:44 -0000

Documentation modified by Les Peters

Les Peters — Sat, 13 Dec 2014 21:14:37 -0000

--- v1
+++ v2
@@ -18,3 +18,27 @@
 ### Changes from last version (6.1.1) ###

 Exec actions now support use of FILENAME substitution
+
+## Installation ##
+
+### Management via iterative process (cron) ###
+
+1. Create installation directory (if not already present) referred hereafter as {install_dir}
+
+

mkdir /opt/omnicheck # or wherever you wish

+ +2. Create logs directory (if being used) + +

mkdir /opt/omnicheck/logs # or wherever you wish

+ +3. Create configuration file or copy one of the samples from this site (see Configuration for details) + +

cd {install_dir}; vi configfile

+ +4. Create rule file(s) in the directory noted as 'home' in the configuration file (see Rule files for details) + +

vi {install_dir}/rules.{nodename}

+ +5. Begin monitoring in the selected tool (cron) + +

/usr/local/bin/perl {install_dir}/omnicheck -F {install_dir}/configfile

Documentation modified by Les Peters

Les Peters — Sat, 13 Dec 2014 21:06:41 -0000

Overview

OmniCheck is a Perl script that is designed to monitor the logfiles of process (or the direct output of processes), perform regular-expression pattern matches against that data, and take a specified notification action.
OmniCheck was originally implemented on HP/UX 9.05, and has been successfully ported to all current revisions of the following operating systems:

HP/UX
Solaris
IRIX
Digital Unix
Win32
Linux
Tandem OSS POSIX environment
Mac OS X (Darwin)
BSD

In short, if the operating system can run Perl version 5.004 patch 4 or later, it can run OmniCheck. If someone knows of a system where this assertion fails, please post a message in OmniCheck's Help forum the project so I can fix whatever is going wrong.

Changes from last version (6.1.1)

Exec actions now support use of FILENAME substitution