$HCISITEDIR exec subdirectories

This table lists the $HCISITEDIR exec subdirectories:

Subdirectory Contents
databases This contains error and recovery database files. To clear the error database, use the Database Administration tool or the hcidbdump command-line utility.
Note: Do not delete files from this directory!
errors Engine output file and core dumps are copied here when the engine ceases operation abnormally, such as during a power failure. Core dumps are on UNIX platforms only. Earlier files can be deleted from this directory.
hcilockmgr Process script and process ID directory for the lock manager.
Note: Do not delete files from this directory!
hcimonitord Process script and process ID directory for the monitor daemon. This contains:
  • cmd_port: Command port number used by other processes to access the monitor daemon’s server socket port. They can then connect and receive status updates or send commands, such as cycle.
  • hcimonitord.err: Errors and warnings are written here.
  • hcimonitord.log: General monitor daemon log file for all log messages; similar to the engine output log file. Currently this is only controlled from the command line -de flag. No eoconfig exists for the Monitor daemon.
  • hcimonitord.log.old: Previous log file, if one exists when the monitor daemon is started.
Note: Do not delete files from this directory!
hcimsgarchive Contains the saved archive files. This is configured on the Site Preference’s Message Archiving tab. Message logs are cycled when they get to the specified size. Cycling a save file causes the current file to close, renames it to old_name.old, and opens a new save file.
monitorShmemFile This is an MSI shared memory file that is used as a key by various programs. These programs locate the shared memory segments containing the engine runtime statistics. Specifically, it is the file used in an ftok invocation which returns a key that is used in the memory attach operations. This file contains no user-usable data. It is a pipe used by the engine to relay thread state and status changes to MonitorD in an event-driven manner.

In UNIX, this is a named pipe used for communication between hcimonitord and all the running engine processes in the site.

In Windows, it is a memory mapped file used to store statistics.

Note: Do not remove this file when processes are running!
processes Subdirectories for each engine process. Each subdirectory is referred to as a "Process Script Directory." This is the relative path name for files that are created by an engine process, such as process logs and SMAT files.