BMC PATROL Agent creates several important directories and files on the PATROL host's disk drive. These files are automatically generated at run time and range from temporary files used for error logging to permanent files that store historical information. The PATROL Agent uses minimal space in the registry.
The following figure shows the structure of a typical PATROL_HOME directory:
The PATROL_HOME directory is the directory in which the PATROL installation process installs PATROL, and in which the PATROL executables and utilities run, write, and read information. The directory contains binaries, knowledge, sounds, images, application defaults, help files, and utilities. The directory is represented as $<PATROL_HOME> in UNIX and PATROL_HOME in Windows.
The following table lists the types of files used by the PATROL Agent and the directory in which it stores these files.
This brief discussion of PATROL's directory structure is not exhaustive. The directories depicted in the figure and the files listed in the PATROL Agent file usage table, are the primary directories and files in a PATROL installation. In your PATROL implementation, additional files and directories may exist depending upon the platforms and installed components.
PATROL Agent file usage
|File type||UNIX path||Description and examples|
|Executable, shared library||$<PATROL_HOME>/bin||Binary directory|
|Agent configuration file (default)||$<PATROL_HOME>/lib/config.default||Agent startup default configuration file|
|Event catalog||$<PATROL_HOME>/lib/knowledge/StdEvents.ctg||Standard Events Catalog|
|Message catalogs||$<PATROL_HOME>/lib/nls/C/1||Directory of message catalogs|
|PSL and OS scripts (shipped)||$<PATROL_HOME>/lib/psl||Directory for shipped PSL and OS (and other KM-defined command types) scripts|
|KMs and Standard Event Catalogs||$<PATROL_HOME>/lib/knowledge||Directory for shipped KMs and Standard Events Catalog|
|Commit lock||$<PATROL_HOME>/lib/commit.lock||File created temporarily during a Commit operation|
|Agent configuration files (customized)||$<PATROL_HOME>/config/ config_<hostName>-<portNumber>||Agent configuration files|
|History file and indices||$<PATROL_HOME>/log/history/<hostName>/<portNumber>/annotate.dat, dir, param.hist||History file and indices|
|<PATROL_HOME>\log\history\<hostName>\<portNumber>\annotate.dat, dir, param.hist|
|PEM event log||$<PATROL_HOME>/log/PEM_<hostName>_<portNumber>.log, archive||Files containing all events for the PATROL Event Manager|
|PEM event lock||$<PATROL_HOME>/log/PEM_<hostName>_<portNumber>.log-lock||Lock on an Event Manager file|
|Error log for the Agent||$<PATROL_HOME>/log/PatrolAgent-<hostName>-<portNumber>.errs.~iter~||File containing agent error messages, and so on|
In a typical setup, the agent runs as a service under the LOCAL SYSTEM account. When user accounts are domain accounts, the LOCAL SYSTEM account does not have the authority to query the domain controller to determine the domain account's home directory. Therefore, the PATROL Agent creates a directory for each user in the profile directory. The agent uses the directory as a substitute for the user's home directory when the home directory cannot be determined due to restrictions in Windows domain security. The profile directory is only used for PATROL Agents running on Windows.