#250101 About inadmissibility of access to Eocortex internal files🔗

Published: 01.31.2025

In the course of its operation, the Eocortex software creates data files and configuration files (hereinafter referred to as "Eocortex internal files") intended exclusively for its internal use by Eocortex components.

Since the Eocortex video surveillance system operation involves numerous operations that are critical to delays and blocking of reading, writing, creating and deleting Eocortex internal files to ensure performance, reliability and fault tolerance (including recovery from power failure), the Eocortex software implements mechanisms for interaction with Eocortex internal files that do not allow parallel work of different processes with the same internal files.

Third-party access to Eocortex internal files (including read mode access) can cause Eocortex video surveillance system failures, including irretrievable loss of data such as system settings and video archive. These failures may be associated, in particular, with competition for access to operating system resources. As a result, the operating system may block the reading, writing, creating or deleting of internal files.

The Eocortex Terms of Use do not provide for the use of third-party tools and services that interact with Eocortex internal files in the course of their operation. The use of such tools and services may lead to fatal failures of the Eocortex software. Therefore, for monitoring and diagnostics of Eocortex software it is allowed to use only standard tools included in the Eocortex software delivery set, as well as HTTP API methods described in the official Eocortex software documentation (access to these tools and methods may be limited by the license).

Thus, third-party access to Eocortex internal files, including the use of third-party tools and services that apply such access, is a violation of the Eocortex software Terms of Use specified in Section 4. "User Obligations" of the Eocortex software End User License Agreement (EULA) .

Below is the list of directories where Eocortex internal files are located:

Allocation of Eocortex internal files in Windows and Windows Server operating systems🔗

Note

The list of the internal files in Windows and Windows Server operating systems contains Windows environment variables %VariableName% and substitutions [Substitution_name]. To determine the actual paths to internal files, it is necessary to replace environment variables and substitutions with their real values according to the following rules:

  • %ProgramData% is a system data directory. It is for an operating system installed by default on the logical drive C: — C:\ProgramData

  • [Archive_drive] is the symbol for the drive on which the archive is located. Examples: D:, E:. There can be several archive drives on one server.

Directories containing internal files:

  • %ProgramData%\ConfigsBackups\

  • %ProgramData%\EocortexConfig\

  • %ProgramData%\EocortexServerConfigs\

  • [Archive_drive]\EocortexArchive\

Allocation of Eocortex internal files in GNU/Linux operating systems🔗

Note

The list of the internal files in GNU/Linux operating systems contains the substitution [archive_drive]. To determine the actual paths to internal files, it is necessary to replace the substitution with its real values according to the following rules:

  • If the drive is mounted automatically, replace [archive_drive] with its GUID.

  • If the drive is mounted manually, replace [archive_drive] with its name specified during mounting.

One server can have multiple archive drives connected in different ways.

  • /opt/EocortexServer/ConfigsBackups/

  • /opt/EocortexServer/EocortexConfig/

  • /opt/EocortexServer/EocortexServerConfigs/

  • /mnt/[archive_drive]/EocortexArchive/

References to documentation on Eocortex standard monitoring tools and APIs🔗