Monitor conf/texis.ini Section

The settings in the [Monitor] section of conf/texis.ini change general properties of the monitor processes.

Run Level
Sets the run level of the Texis Monitor. Its value is an integer whose bits indicate the following: bit 0 is whether to run as overall Texis Monitor, bit 1 is whether to exit if the default database is removed. Internal/unsupported use. Normally 1. Added in version 3.01.981800000 Feb 9 2001. See also this setting in the [Scheduler] section.

Log File
Contains the file name that monitor should log to. The default is monitor.log in the texis subdirectory of the install directory. This can be overridden with the -o command-line option.

Lock File
On non-Windows platforms, this is the name of the lock file that database monitors check as an indicator of whether to exit when monitor -k is issued. It defaults to texis/.dbmonlck in the install directory. This file and its parent directory (texis) should be writable by the Texis user. Added in version 3.01.985300000 Mar 22 2001.

Log Native IO
On Windows platforms, whether to use native system calls for log file I/O. The default is 0 (off); set to 1 to enabled. Generally enabled only at request of tech support.

Log Reopen
If 1, re-open the log file for every message, instead of keeping it open between messages. Generally enabled only at request of tech support.

Pid File
The file that the Texis Monitor writes its process ID to. Normally empty (no file). Internal use.

Trace Dns
Trace DNS calls according to given integer level (default 0 for no tracing). Same format as the Vortex <urlcp tracedns> setting. For debugging/tech support use.

Trace Socket
Trace socket calls according to given integer level (default 0 for no tracing). Same format as the Vortex <urlcp traceskt> setting. For debugging/tech support use.

Trace Pipe
Trace pipe calls according to given integer level (default 0 for no tracing). Same format as the Vortex -tracepipe command-line option. For debugging/tech support use.

Trace Fcgi
Trace FastCGI calls according to given integer level (default 0 for no tracing). For debugging/tech support use.

If set this will write a time stamp to the log file every Timestamp seconds. This can be used to make sure the monitor is still running. This is set to 0 by default, which disables this feature.

If you are running a monitor at a terminal, and there is an interactive display (e.g. ltest), this setting sets the default refresh interval for the display. The default is 5 seconds. This can be modified while the program is running by hitting a numeric key.

Keyboard Read
This is related to Refresh, and controls how often the keyboard is checked for input.

This controls how often the semaphore is checked to make sure that it has not become stuck, which would cause the database to be unusable. The default is 10 (seconds).

Semaphore Timeout
This controls how long the semaphore should be ungettable before it is considered stuck. The default is 10 (seconds).


How often the database should be checked for removal. The default is 30 seconds; prior to Texis version 7 it was 60 (1 minute). If you frequently create and delete databases this will prevent the database monitor process from running too long.

DB Quiet
Sets the time in seconds that the database monitor should keep watching the database if there are no accesses to the database. Once this idle time has elapsed with no accesses, the database monitor will exit. The default is 120 (2 minutes). This value plus Removal should be larger than any of the settings that periodically access the database, e.g [Chkind] Refresh or [Monitor] DB Cleanup Interval, so that the latter do not artificially cause the database to appear too-recently-used when DB Quiet looks for idleness.

Upgrade SYSTEM tables
Whether to attempt to upgrade older existing databases' system tables to the latest schema, e.g. whether to add the PARAMS column to the SYSINDEX table. Upgrading is recommended, as this column is needed for some newer index features. Added in version 3.01.992053000 20010608; databases created with that version or later already have up to date system tables schemas regardless of this setting. Default is 0 (off).

How often the database statistics should be updated, in seconds. The default is 3600 (1 hour).

Stats Block
If nonzero, a blocking connect() call will be used by the statistics monitor client. This is normally 0 (off), except under Linux 1.x kernels where it defaults to on to avoid a bug in the kernel.

Mem Limit
Virtual-memory limit for monitors: if a monitor process exceeds this limit it will exit. Default is no limit. Can have MB etc. suffix, e.g. "100MB" for one hundred megabytes. Used for debugging.

Whether to attempt to fork() the monitor program to start it when possible (Unix), for certain instances. Bit 0 controls forking for monitor -s (internal statistics gathering), bit 1 controls monitor -C.

Max Scheduler Fails
Maximum number of failed attempts to start Vortex <schedule> jobs before exiting. Default is 5. Debugging use. Note that a failed or non-zero-exiting script is not generally considered a failed attempt at starting Vortex jobs.

Integer whose bit flags control some log messages. If bit 0 is set, database monitors starting and stopping are logged. If bit 1 is set, semaphore removals are logged. The default value is 1.

Use Ddic Mutex
Boolean: Whether to use a mutex to protect internal DDIC usage. The default is yes. Turning this off can potentially cause monitor problems, and is generally recommended only at the request of tech support. Added in version 5.01.1239305000 20090409.

DB Cleanup Interval

Integer number of seconds between database cleanups, which look for deleted and temporary indexes and tables and try to remove them (if no longer in use). This cleanup also happens automatically as needed - e.g. before index creation - but cleaning up periodically may save some disk space sooner. The default is 180 seconds. Added in version 6.00.1338325000 20120529. Before Texis version 7, the default was 60 seconds. The value should be less than [Monitor] DB Quiet (see discussion there).

DB Cleanup Verbose

Integer whose bit flags control some log messages about database cleanup housekeeping (e.g. removal of unneeded temporary or deleted indexes and tables) when conducted by the Database Monitor. A bit-wise OR of the following values:

  • 0x01: Report successful removal of temporary/deleted indexes/tables.

  • 0x02: Report failed removal of such indexes/tables.

  • 0x04: Report on in-use checks of temporary indexes/tables.

The default is 0 (i.e. no messages). Note that these cleanup actions may also be handled by any Texis process that accesses the database; see also the dbcleanupverbose SQL property. Added in version 6.00.1339712000 20120614.

Copyright © Thunderstone Software     Last updated: Dec 10 2018
Copyright © 2020 Thunderstone Software LLC. All rights reserved.