Command-line Options

Command-Line Options

The command-line options are as follows:

• -F {file} (alternate: --config-file)

Mandatory: provides the filename of the configuration file.

• -I (alternate: --init)

Mandatory for manual initialization: causes OmniCheck to establish a baseline byte offset for each file(s) to be monitored. This function will now occur on first invocation, leaving this command-line option deprecated.

• -Z (alternate: --zero)

Optional, used during manual initialization: causes OmniCheck to set the byte offset for each file(s) to be monitored to zero.

• --re_init

Optional: causes OmniCheck to overwrite a previous initialization.

• -P (alternate: --persistent)

Mandatory for daemon execution: causes OmniCheck to enter an event loop; each pass through the event loop will take no less than the number of seconds indicated by the interval configuration file entry value (see below). If it takes more than that, then at the end of that pass, it starts another pass. If there is time left, it will sleep. If you want to wake it up early, send the process ID (PID) a SIGHUP.

NOTE: may not be used with files that consist of multiple physical lines.

• -D {value} (alternate: --debug)

Optional: sends debugging log statements to OmniCheck's err file. Possible values:

debug
info
notice (default value)
warn
err
crit
alert
emer

• -H (alternate: --help)

Optional: displays a command-line help screen.

• -T (alternate: --test)

Optional: enables test input mode. In this mode, OmniCheck will read standard input as the content to be monitored: all notifications are simulated and sent to STDOUT. When testing data intended for a single block of a multiple block configuration, use the -B/--block option (described below). Also,

• -B or --block

Optional: test block value. When used with -T/--test (described above), this option will restrict the activity of OmniCheck to the configuration block indicated by this option. If not used during test input mode, the first, or 'main', block will be used.